Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 023289a153675238f97b7e218cbd7ca9c08f0b43b12d46008b8ed2bd7cf5ccc4

Tx prefix hash: 48c879979fdccf9b30ad73e3f62cc410a0eaf7387a72500a4eb07f0b2d57104a
Tx public key: b1d4405ecf2b86bcbcb6e8d68029192b339ab63cc9b785506f323d58a45058e8
Timestamp: 1705533078 Timestamp [UCT]: 2024-01-17 23:11:18 Age [y:d:h:m:s]: 01:303:23:05:03
Block: 937592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476078 RingCT/type: yes/0
Extra: 01b1d4405ecf2b86bcbcb6e8d68029192b339ab63cc9b785506f323d58a45058e802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d981d1ba2f30730dad04751f4825c6eaded91f72875eae895176a00d8446f77 0.600000000000 1395652 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": 937602, "vin": [ { "gen": { "height": 937592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d981d1ba2f30730dad04751f4825c6eaded91f72875eae895176a00d8446f77" } } ], "extra": [ 1, 177, 212, 64, 94, 207, 43, 134, 188, 188, 182, 232, 214, 128, 41, 25, 43, 51, 154, 182, 60, 201, 183, 133, 80, 111, 50, 61, 88, 164, 80, 88, 232, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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