Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1246f655313d5d4adaf5f7a5106b66a0b8e2c9467001462a453959dfc8150b6

Tx prefix hash: f5d3ca7a3bf0a108492545e9bfc091e9714ad1a8100a16cf2bb5dc7eb14a7e2a
Tx public key: ac68d776832fdb76a233e8d661dcef5462852786c2a3e208a974dfc2a8f9726d
Timestamp: 1624034932 Timestamp [UCT]: 2021-06-18 16:48:52 Age [y:d:h:m:s]: 03:270:05:19:30
Block: 279837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 959571 RingCT/type: yes/0
Extra: 01ac68d776832fdb76a233e8d661dcef5462852786c2a3e208a974dfc2a8f9726d02110000001e9c1fbdcc000000000000000000

1 output(s) for total of 72.579453526000 dcy

stealth address amount amount idx
00: e52a626e111080cc8f8ba17824c329e62dfdbb9b529b6cb9c5f26a456c850c9e 72.579453526000 586004 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": 279847, "vin": [ { "gen": { "height": 279837 } } ], "vout": [ { "amount": 72579453526, "target": { "key": "e52a626e111080cc8f8ba17824c329e62dfdbb9b529b6cb9c5f26a456c850c9e" } } ], "extra": [ 1, 172, 104, 215, 118, 131, 47, 219, 118, 162, 51, 232, 214, 97, 220, 239, 84, 98, 133, 39, 134, 194, 163, 226, 8, 169, 116, 223, 194, 168, 249, 114, 109, 2, 17, 0, 0, 0, 30, 156, 31, 189, 204, 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