Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 635ebdf2b47507d435c1f779feefc1edae50c7cf5f3278287538274d611c3f0b

Tx prefix hash: d69925e624f9c83dee48649d8e6e6b93b05381e762f5328c4fb141b0de1cd8a3
Tx public key: 9e493bfbb657f4754e3a28948de2d4d87345fde0157eb113a49e96b01caee7d7
Timestamp: 1727019223 Timestamp [UCT]: 2024-09-22 15:33:43 Age [y:d:h:m:s]: 00:173:00:31:40
Block: 1115752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123481 RingCT/type: yes/0
Extra: 019e493bfbb657f4754e3a28948de2d4d87345fde0157eb113a49e96b01caee7d7021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3c9e9ce7837d0fca1d3f230564be17264ba8527329c1505147f4ba7eaaac970 0.600000000000 1595993 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": 1115762, "vin": [ { "gen": { "height": 1115752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c9e9ce7837d0fca1d3f230564be17264ba8527329c1505147f4ba7eaaac970" } } ], "extra": [ 1, 158, 73, 59, 251, 182, 87, 244, 117, 78, 58, 40, 148, 141, 226, 212, 216, 115, 69, 253, 224, 21, 126, 177, 19, 164, 158, 150, 176, 28, 174, 231, 215, 2, 17, 0, 0, 0, 4, 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