Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db7f4396087c6c7956b401153ad798d57f8e5ce3a6c2ad0fa583091a1f5053dc

Tx prefix hash: 86e15769a26c75277a9d7f96959c04fb2bcfec90f45869e9ca3d2681dc4914b7
Tx public key: 70540426771faea70aaa6bb2c4cb49ca1ac1b9c02f8cec79a2d988db18ac79b6
Timestamp: 1721471605 Timestamp [UCT]: 2024-07-20 10:33:25 Age [y:d:h:m:s]: 00:269:19:15:25
Block: 1069755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192753 RingCT/type: yes/0
Extra: 0170540426771faea70aaa6bb2c4cb49ca1ac1b9c02f8cec79a2d988db18ac79b6021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deeb4c998bec861a9d2f8699d064d12db39d568d306fe03eed2c57ce3c2fc3ef 0.600000000000 1541312 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": 1069765, "vin": [ { "gen": { "height": 1069755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deeb4c998bec861a9d2f8699d064d12db39d568d306fe03eed2c57ce3c2fc3ef" } } ], "extra": [ 1, 112, 84, 4, 38, 119, 31, 174, 167, 10, 170, 107, 178, 196, 203, 73, 202, 26, 193, 185, 192, 47, 140, 236, 121, 162, 217, 136, 219, 24, 172, 121, 182, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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