Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d2e15861b2f8eba5dbc1af3bd0eee1b9f2dbc933be795c0a15222be35d8b409

Tx prefix hash: 229a8bcc31467d3dafdb734f1348015e2715045fb73a5fdca959a8373b0a908a
Tx public key: 0aec96f009f7e98a409b6e272142c2a72ca5481910c01235a7e237cc40c8f77a
Timestamp: 1577725638 Timestamp [UCT]: 2019-12-30 17:07:18 Age [y:d:h:m:s]: 05:017:14:10:51
Block: 35173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1162550 RingCT/type: yes/0
Extra: 010aec96f009f7e98a409b6e272142c2a72ca5481910c01235a7e237cc40c8f77a02110000000e4943cd9f000000000000000000

1 output(s) for total of 469.308159151000 dcy

stealth address amount amount idx
00: 48e2e378f19d6ed02da4a24239e27efe01dac4f4416ea4b9ce0ab2930ff2966b 469.308159151000 59245 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": 35183, "vin": [ { "gen": { "height": 35173 } } ], "vout": [ { "amount": 469308159151, "target": { "key": "48e2e378f19d6ed02da4a24239e27efe01dac4f4416ea4b9ce0ab2930ff2966b" } } ], "extra": [ 1, 10, 236, 150, 240, 9, 247, 233, 138, 64, 155, 110, 39, 33, 66, 194, 167, 44, 165, 72, 25, 16, 192, 18, 53, 167, 226, 55, 204, 64, 200, 247, 122, 2, 17, 0, 0, 0, 14, 73, 67, 205, 159, 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