Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 720a8a43ef04d79cedb59b2bc8e4b29ffc6bad8bf06e569e09002a19e0a2b5f5

Tx prefix hash: 31fba4bbe1dfd4f37eb7e38abfb9ed6bfb80ee96921e48282ea45f904ab8dd82
Tx public key: d3d0c1f1b6e891b38a6cd49695c3da9db04c408723e9d4296b3f1a07d4256a3c
Timestamp: 1745987857 Timestamp [UCT]: 2025-04-30 04:37:37 Age [y:d:h:m:s]: 00:007:00:28:24
Block: 1272494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5012 RingCT/type: yes/0
Extra: 01d3d0c1f1b6e891b38a6cd49695c3da9db04c408723e9d4296b3f1a07d4256a3c0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30a56682cff07647a97a91747cd268627e5314fbc53f96d94f4b1dfe3a4e7aaa 0.600000000000 1759769 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": 1272504, "vin": [ { "gen": { "height": 1272494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30a56682cff07647a97a91747cd268627e5314fbc53f96d94f4b1dfe3a4e7aaa" } } ], "extra": [ 1, 211, 208, 193, 241, 182, 232, 145, 179, 138, 108, 212, 150, 149, 195, 218, 157, 176, 76, 64, 135, 35, 233, 212, 41, 107, 63, 26, 7, 212, 37, 106, 60, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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