Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2c74cbc4cb346fcbd7778d165d6f2514a8e213aac4061c7406baa14d9ffcbe53

Tx prefix hash: ae6f68f98d08b959e91b33729f1c7504fcb7f8a738ff8719ebbc01c081dd514b
Tx public key: 54fe658a3f39ba192a85a78dfc10fa60629836a685f925262dd6a3c4f7db9cd3
Timestamp: 1705391878 Timestamp [UCT]: 2024-01-16 07:57:58 Age [y:d:h:m:s]: 01:078:12:21:06
Block: 936419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317213 RingCT/type: yes/0
Extra: 0154fe658a3f39ba192a85a78dfc10fa60629836a685f925262dd6a3c4f7db9cd302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2834062e3d016a51b43d0f44f6d6effd763b53a4818c88e67c23fe51eda7c1c2 0.600000000000 1394445 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 936429, "vin": [ { "gen": { "height": 936419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2834062e3d016a51b43d0f44f6d6effd763b53a4818c88e67c23fe51eda7c1c2" } } ], "extra": [ 1, 84, 254, 101, 138, 63, 57, 186, 25, 42, 133, 167, 141, 252, 16, 250, 96, 98, 152, 54, 166, 133, 249, 37, 38, 45, 214, 163, 196, 247, 219, 156, 211, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8