Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b47ec1ae24d273ef72a7b7207b609f255031669ab348be17f7618e2cfc48abf0

Tx prefix hash: dbc346c3f1f749081c72e1ed5fabe2cfd2e21148538242349c8836607fc25379
Tx public key: b58c9e636eb391527b35a3e016a4ff7d35fbfc2dc0b3624cab6da0f7d60987d2
Timestamp: 1712056727 Timestamp [UCT]: 2024-04-02 11:18:47 Age [y:d:h:m:s]: 00:297:11:53:29
Block: 991672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212927 RingCT/type: yes/0
Extra: 01b58c9e636eb391527b35a3e016a4ff7d35fbfc2dc0b3624cab6da0f7d60987d202110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 481fa3b0495818f4aee07d8fb48ffcc7964abf313a86203e040e55a02d7fa0dd 0.600000000000 1452008 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": 991682, "vin": [ { "gen": { "height": 991672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "481fa3b0495818f4aee07d8fb48ffcc7964abf313a86203e040e55a02d7fa0dd" } } ], "extra": [ 1, 181, 140, 158, 99, 110, 179, 145, 82, 123, 53, 163, 224, 22, 164, 255, 125, 53, 251, 252, 45, 192, 179, 98, 76, 171, 109, 160, 247, 214, 9, 135, 210, 2, 17, 0, 0, 0, 5, 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