Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c31f13408077ace72024da6b27044b41de9eb3ca0b02942450785b123e6d2d6a

Tx prefix hash: 444226598e81cacf9a1156ec327fc806c2e2120c11ee8e3d72f5d288fc9b999f
Tx public key: 2459129c5cf1bc4297b9c8a66903f35f16f3dd98d079c294e9aaa224b84130d8
Timestamp: 1576447195 Timestamp [UCT]: 2019-12-15 21:59:55 Age [y:d:h:m:s]: 05:321:14:36:56
Block: 27870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1374063 RingCT/type: yes/0
Extra: 012459129c5cf1bc4297b9c8a66903f35f16f3dd98d079c294e9aaa224b84130d802110000001ed81c26c0000000000000000000

1 output(s) for total of 496.199115767000 dcy

stealth address amount amount idx
00: 287f3394ccc770eb69ac816fabcab0c0e8c5165c3bacdde6e7b93677b47c7d43 496.199115767000 46026 of 0

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": 27880, "vin": [ { "gen": { "height": 27870 } } ], "vout": [ { "amount": 496199115767, "target": { "key": "287f3394ccc770eb69ac816fabcab0c0e8c5165c3bacdde6e7b93677b47c7d43" } } ], "extra": [ 1, 36, 89, 18, 156, 92, 241, 188, 66, 151, 185, 200, 166, 105, 3, 243, 95, 22, 243, 221, 152, 208, 121, 194, 148, 233, 170, 162, 36, 184, 65, 48, 216, 2, 17, 0, 0, 0, 30, 216, 28, 38, 192, 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