Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87749c0676de3ff095e9803fa0994f3bb312b50ec3246bc5f9c6f2c1a85c1918

Tx prefix hash: b5bd9fae0c56598a950f85d507b214114cdcbff0e577fcf5bebaed714cae574c
Tx public key: cde5bc5e76ae7fda975631c53c0318e6512ca9d47c22a5d48beb1e6073c96e43
Timestamp: 1580480391 Timestamp [UCT]: 2020-01-31 14:19:51 Age [y:d:h:m:s]: 04:327:05:37:55
Block: 55813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125160 RingCT/type: yes/0
Extra: 01cde5bc5e76ae7fda975631c53c0318e6512ca9d47c22a5d48beb1e6073c96e43021100000003dcee4b4d000000000000000000

1 output(s) for total of 400.930583806000 dcy

stealth address amount amount idx
00: 88ea08cc9ac6d12af0289b27c3319a51f16b3a4d6986b3e9b9b671cd79af5d3b 400.930583806000 102978 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": 55823, "vin": [ { "gen": { "height": 55813 } } ], "vout": [ { "amount": 400930583806, "target": { "key": "88ea08cc9ac6d12af0289b27c3319a51f16b3a4d6986b3e9b9b671cd79af5d3b" } } ], "extra": [ 1, 205, 229, 188, 94, 118, 174, 127, 218, 151, 86, 49, 197, 60, 3, 24, 230, 81, 44, 169, 212, 124, 34, 165, 212, 139, 235, 30, 96, 115, 201, 110, 67, 2, 17, 0, 0, 0, 3, 220, 238, 75, 77, 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