Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b25834c2f349f7fc89adbabb35337eb5c8ae1834223c461ad6e56734884827c8

Tx prefix hash: 585e9297acd8a86f22dfd0c5b422da816a46fa95b111a6ecf9b57df3d597f2ee
Tx public key: 149dafdf48cdfe727d38b5e9685a41a0752727c6182dc75c49cb7be24462884c
Timestamp: 1716711521 Timestamp [UCT]: 2024-05-26 08:18:41 Age [y:d:h:m:s]: 00:334:11:31:00
Block: 1030300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239070 RingCT/type: yes/0
Extra: 01149dafdf48cdfe727d38b5e9685a41a0752727c6182dc75c49cb7be24462884c0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dd1fedf6ce78c1428742e3d61d321ba9a125c17fbd6f91611b3366f17c6dcd4 0.600000000000 1498555 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": 1030310, "vin": [ { "gen": { "height": 1030300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dd1fedf6ce78c1428742e3d61d321ba9a125c17fbd6f91611b3366f17c6dcd4" } } ], "extra": [ 1, 20, 157, 175, 223, 72, 205, 254, 114, 125, 56, 181, 233, 104, 90, 65, 160, 117, 39, 39, 198, 24, 45, 199, 92, 73, 203, 123, 226, 68, 98, 136, 76, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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