Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 211cbdf97b525e096bc8466630722ab4fb731040f96e037442062225d1712aa1

Tx prefix hash: 259e488b91c5e1276bd6b9680d58a77f3891c696ef93e783c25de7cb36854f17
Tx public key: 809662faea252c5a6f9e0fe9d410b85e72ab2f1622210a69d8c28045a2cdf269
Timestamp: 1699143104 Timestamp [UCT]: 2023-11-05 00:11:44 Age [y:d:h:m:s]: 01:212:21:41:14
Block: 884895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413155 RingCT/type: yes/0
Extra: 01809662faea252c5a6f9e0fe9d410b85e72ab2f1622210a69d8c28045a2cdf269021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.717753854000 dcy

stealth address amount amount idx
00: 16a58c05318b0a3e8a9b14775cec3dfe08fd5626cb2aeb8df9c0def76a57e3f6 0.717753854000 1340644 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": 884905, "vin": [ { "gen": { "height": 884895 } } ], "vout": [ { "amount": 717753854, "target": { "key": "16a58c05318b0a3e8a9b14775cec3dfe08fd5626cb2aeb8df9c0def76a57e3f6" } } ], "extra": [ 1, 128, 150, 98, 250, 234, 37, 44, 90, 111, 158, 15, 233, 212, 16, 184, 94, 114, 171, 47, 22, 34, 33, 10, 105, 216, 194, 128, 69, 162, 205, 242, 105, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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