Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5913f229a91d38400db37200ec693deec45661a3816dd71532a3d92ac47db36a

Tx prefix hash: abd4e402a006cd3bec05b53089785b3582089d3717ea47167e4a87cb46f4816a
Tx public key: c3e5d06737853c1f92ced9ed50d5df0957f34bffa41c43ea7765ce7eb87f09fd
Timestamp: 1717291293 Timestamp [UCT]: 2024-06-02 01:21:33 Age [y:d:h:m:s]: 00:235:23:15:35
Block: 1035102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168825 RingCT/type: yes/0
Extra: 01c3e5d06737853c1f92ced9ed50d5df0957f34bffa41c43ea7765ce7eb87f09fd021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1e94e430bb0b5f559c1e2726dbee9962af81d03c4b748e17e0ff8e3781c5d70 0.600000000000 1503621 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": 1035112, "vin": [ { "gen": { "height": 1035102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1e94e430bb0b5f559c1e2726dbee9962af81d03c4b748e17e0ff8e3781c5d70" } } ], "extra": [ 1, 195, 229, 208, 103, 55, 133, 60, 31, 146, 206, 217, 237, 80, 213, 223, 9, 87, 243, 75, 255, 164, 28, 67, 234, 119, 101, 206, 126, 184, 127, 9, 253, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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