Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa121c05e8768c0285119a261ce6e876743bca2b3cf79dcf1388c354a30ceec7

Tx prefix hash: 8e94c5f4686904a9b4f43647ee5cdbecabcecd4bb469d2744b4ae9d3d652a5d3
Tx public key: 0ad5862f46def98a712228550567894129e742293f67e4a7683a0ad83c9c8d80
Timestamp: 1700918905 Timestamp [UCT]: 2023-11-25 13:28:25 Age [y:d:h:m:s]: 01:172:08:14:20
Block: 899370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384359 RingCT/type: yes/0
Extra: 010ad5862f46def98a712228550567894129e742293f67e4a7683a0ad83c9c8d80021100000002faf35c9c000000000000000000

1 output(s) for total of 0.642708181000 dcy

stealth address amount amount idx
00: 427dc9d2060311038ad45b1b28b9d3273ce37c230f540719dd642df0d341d7db 0.642708181000 1355823 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": 899380, "vin": [ { "gen": { "height": 899370 } } ], "vout": [ { "amount": 642708181, "target": { "key": "427dc9d2060311038ad45b1b28b9d3273ce37c230f540719dd642df0d341d7db" } } ], "extra": [ 1, 10, 213, 134, 47, 70, 222, 249, 138, 113, 34, 40, 85, 5, 103, 137, 65, 41, 231, 66, 41, 63, 103, 228, 167, 104, 58, 10, 216, 60, 156, 141, 128, 2, 17, 0, 0, 0, 2, 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