Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30b9939379a3f0715bc97b16da480e47c8f57d83b08e446aed759667f4cbb830

Tx prefix hash: 517b9a44fa3cbdc6e78774966fe35d34b8f4775bdd6eebe8bee639532569a7d0
Tx public key: 48791471ca01e409a5b9fb84d7e326707bad1fa597b3dc428177f66b095d1cb4
Timestamp: 1726853034 Timestamp [UCT]: 2024-09-20 17:23:54 Age [y:d:h:m:s]: 00:112:03:22:10
Block: 1114371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80188 RingCT/type: yes/0
Extra: 0148791471ca01e409a5b9fb84d7e326707bad1fa597b3dc428177f66b095d1cb4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74ff96e1332adfb7fc70910fc3d5f49f960b4f29554bf2d11d997fae3f0fec4a 0.600000000000 1594172 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": 1114381, "vin": [ { "gen": { "height": 1114371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74ff96e1332adfb7fc70910fc3d5f49f960b4f29554bf2d11d997fae3f0fec4a" } } ], "extra": [ 1, 72, 121, 20, 113, 202, 1, 228, 9, 165, 185, 251, 132, 215, 227, 38, 112, 123, 173, 31, 165, 151, 179, 220, 66, 129, 119, 246, 107, 9, 93, 28, 180, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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