Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0391ea374aa702bcab28c8df304702b700a02ecc1c1ceffa599f6ca7cd4ae2d5

Tx prefix hash: 4a8b040bc67c63224904e173680aa4d2983ea2b715eef8a9392617098c13a28a
Tx public key: b0f5a27babd2d5feecf5673b94fdec219b7b0cb40d3023e7f0b476be30e9c4b7
Timestamp: 1748469466 Timestamp [UCT]: 2025-05-28 21:57:46 Age [y:d:h:m:s]: 00:183:08:56:40
Block: 1293040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128761 RingCT/type: yes/0
Extra: 01b0f5a27babd2d5feecf5673b94fdec219b7b0cb40d3023e7f0b476be30e9c4b7021100000005df096e52000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d12b0f60729591402de8dcb807b1cd98c0ec8a97b837a9a174d707adf30a9ab 0.600000000000 1780511 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": 1293050, "vin": [ { "gen": { "height": 1293040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d12b0f60729591402de8dcb807b1cd98c0ec8a97b837a9a174d707adf30a9ab" } } ], "extra": [ 1, 176, 245, 162, 123, 171, 210, 213, 254, 236, 245, 103, 59, 148, 253, 236, 33, 155, 123, 12, 180, 13, 48, 35, 231, 240, 180, 118, 190, 48, 233, 196, 183, 2, 17, 0, 0, 0, 5, 223, 9, 110, 82, 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