Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fbfd4c02929aabd1811328450e2980342590eecc4ccb077b7502bc8e07cf15f

Tx prefix hash: e22b47ea1e2167a8e22fc2786344bed1738d995d1574f28a5f88c66fccb6a460
Tx public key: 0e779ed4f11c5b4788dd38f5a9d1c032970e01a7bfbce04f87e22cfc6cc2113d
Timestamp: 1706351250 Timestamp [UCT]: 2024-01-27 10:27:30 Age [y:d:h:m:s]: 01:278:08:34:19
Block: 944380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457746 RingCT/type: yes/0
Extra: 010e779ed4f11c5b4788dd38f5a9d1c032970e01a7bfbce04f87e22cfc6cc2113d02110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12fee435c6a9a1b3b180ad9079b6f8208d4429c59042136a72e1680beaa4c532 0.600000000000 1402616 of 15

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": 944390, "vin": [ { "gen": { "height": 944380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12fee435c6a9a1b3b180ad9079b6f8208d4429c59042136a72e1680beaa4c532" } } ], "extra": [ 1, 14, 119, 158, 212, 241, 28, 91, 71, 136, 221, 56, 245, 169, 209, 192, 50, 151, 14, 1, 167, 191, 188, 224, 79, 135, 226, 44, 252, 108, 194, 17, 61, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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