Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94b644fa39a9cc7cd73341a717efc3529a71a5592d03535a7c07b7e1aa5a20da

Tx prefix hash: 2566351b5cf3c40a81629faa8db24816f975ae518f5bd09a4fc079239a42c590
Tx public key: 956e4a6e5fb061627ff87f7d2cd686174e18ad9039f992f60d9658b75b040ecb
Timestamp: 1713008711 Timestamp [UCT]: 2024-04-13 11:45:11 Age [y:d:h:m:s]: 00:360:17:54:12
Block: 999581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257910 RingCT/type: yes/0
Extra: 01956e4a6e5fb061627ff87f7d2cd686174e18ad9039f992f60d9658b75b040ecb0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7af2980ce86af2e99b5bdfd45207baae410965473b1b611a887d9ae48f87fc73 0.600000000000 1460063 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": 999591, "vin": [ { "gen": { "height": 999581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7af2980ce86af2e99b5bdfd45207baae410965473b1b611a887d9ae48f87fc73" } } ], "extra": [ 1, 149, 110, 74, 110, 95, 176, 97, 98, 127, 248, 127, 125, 44, 214, 134, 23, 78, 24, 173, 144, 57, 249, 146, 246, 13, 150, 88, 183, 91, 4, 14, 203, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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