Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c74ad38144d6a3bbe87d971b5512348f88d0184b6b7fce629f0d0e32e346ffab

Tx prefix hash: b6cbff60d96b934c9ea92e2b8b36bb0d632dabc055ab2b1f79a7464fe3983665
Tx public key: d6245b1b327f432e020b4bb8ca6ca4454f7410295660c2a98dad6e1202898898
Timestamp: 1714163150 Timestamp [UCT]: 2024-04-26 20:25:50 Age [y:d:h:m:s]: 00:343:07:26:18
Block: 1009154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245420 RingCT/type: yes/0
Extra: 01d6245b1b327f432e020b4bb8ca6ca4454f7410295660c2a98dad6e12028988980211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8c9d54e43ba83b77f4bc74d9be13f45b998bf32b2f360d6ae37e4b3d4218bf4 0.600000000000 1470748 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": 1009164, "vin": [ { "gen": { "height": 1009154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8c9d54e43ba83b77f4bc74d9be13f45b998bf32b2f360d6ae37e4b3d4218bf4" } } ], "extra": [ 1, 214, 36, 91, 27, 50, 127, 67, 46, 2, 11, 75, 184, 202, 108, 164, 69, 79, 116, 16, 41, 86, 96, 194, 169, 141, 173, 110, 18, 2, 137, 136, 152, 2, 17, 0, 0, 0, 1, 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