Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15f510ef8b165a8189d86fc717a872795d85d759a1b326c39571f7ffc6a1b6ed

Tx prefix hash: 1c7adf7124ba1b3c472815a25428dee8adbf43ffc8a56cb625d98510e4857e5a
Tx public key: 771650f15286d5f2ed23196f006bb83a25492cee0dad7a27fce71b383d026f32
Timestamp: 1718501466 Timestamp [UCT]: 2024-06-16 01:31:06 Age [y:d:h:m:s]: 00:346:20:47:15
Block: 1045148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247902 RingCT/type: yes/0
Extra: 01771650f15286d5f2ed23196f006bb83a25492cee0dad7a27fce71b383d026f320211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90970a5d1f6b8f6dca8585ae52b1fbd0e9492f1061d7b0c24b96b389f8ac6739 0.600000000000 1514645 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": 1045158, "vin": [ { "gen": { "height": 1045148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90970a5d1f6b8f6dca8585ae52b1fbd0e9492f1061d7b0c24b96b389f8ac6739" } } ], "extra": [ 1, 119, 22, 80, 241, 82, 134, 213, 242, 237, 35, 25, 111, 0, 107, 184, 58, 37, 73, 44, 238, 13, 173, 122, 39, 252, 231, 27, 56, 61, 2, 111, 50, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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