Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f0f88daf13a2f48126a0358a0eb9ffeac6b51cb4c0ffc4e86fedae212c569b

Tx prefix hash: bf1057ba077feeff223ac812a75a07c1139fcc5fcb154dac954eeea199962fa5
Tx public key: ad70427e0a5ba2920975b9bfd761dfc270ee77222a59b524cfff5ea1d87c1ef2
Timestamp: 1700870509 Timestamp [UCT]: 2023-11-25 00:01:49 Age [y:d:h:m:s]: 01:055:01:43:57
Block: 898967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300738 RingCT/type: yes/0
Extra: 01ad70427e0a5ba2920975b9bfd761dfc270ee77222a59b524cfff5ea1d87c1ef202110000000afaf35c9c000000000000000000

1 output(s) for total of 0.644687330000 dcy

stealth address amount amount idx
00: 3456e4ee2d54cd8b56e6a2fd13b495d182b6f4f3f5261e4553b9a8f3a934631b 0.644687330000 1355404 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": 898977, "vin": [ { "gen": { "height": 898967 } } ], "vout": [ { "amount": 644687330, "target": { "key": "3456e4ee2d54cd8b56e6a2fd13b495d182b6f4f3f5261e4553b9a8f3a934631b" } } ], "extra": [ 1, 173, 112, 66, 126, 10, 91, 162, 146, 9, 117, 185, 191, 215, 97, 223, 194, 112, 238, 119, 34, 42, 89, 181, 36, 207, 255, 94, 161, 216, 124, 30, 242, 2, 17, 0, 0, 0, 10, 250, 243, 92, 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