Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11fe53f49b1befa713d5c701d0e4e86318b3bde019f40d27ba6493239ac6e7cf

Tx prefix hash: f2c175eb672cbb14401915c9212f9649129e6ea8fb4e1645f9fc7076561a7ddd
Tx public key: b410b481243622fcce23b065450cb5ac2694a34c24c44da03ec2caccf81f4b8a
Timestamp: 1583537709 Timestamp [UCT]: 2020-03-06 23:35:09 Age [y:d:h:m:s]: 04:296:07:21:23
Block: 77831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106297 RingCT/type: yes/0
Extra: 01b410b481243622fcce23b065450cb5ac2694a34c24c44da03ec2caccf81f4b8a0211000000195143fba2000000000000000000

1 output(s) for total of 338.933409903000 dcy

stealth address amount amount idx
00: dc5f68a435790a7919595a409223cde21e969ed22a7237c560d8715ae5232a13 338.933409903000 143042 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": 77841, "vin": [ { "gen": { "height": 77831 } } ], "vout": [ { "amount": 338933409903, "target": { "key": "dc5f68a435790a7919595a409223cde21e969ed22a7237c560d8715ae5232a13" } } ], "extra": [ 1, 180, 16, 180, 129, 36, 54, 34, 252, 206, 35, 176, 101, 69, 12, 181, 172, 38, 148, 163, 76, 36, 196, 77, 160, 62, 194, 202, 204, 248, 31, 75, 138, 2, 17, 0, 0, 0, 25, 81, 67, 251, 162, 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