Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b410586489f960a684cde3ab8227e8607c4a418fcead42f0793d998f305065e5

Tx prefix hash: cdf07838e680871c2a673f3fe7f4455aa7bb157f80e5dc274139812b1f9e7646
Tx public key: 3d9c9b47154bcabb24a5035be2af80d6d370e73b3727e50849d36d4f9de9d4e9
Timestamp: 1718038060 Timestamp [UCT]: 2024-06-10 16:47:40 Age [y:d:h:m:s]: 00:301:00:47:03
Block: 1041289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215121 RingCT/type: yes/0
Extra: 013d9c9b47154bcabb24a5035be2af80d6d370e73b3727e50849d36d4f9de9d4e90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc5e8fd2b339941c7d73feb701d5db39215316397e6f0ea62334fdd0fb94e32d 0.600000000000 1509954 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": 1041299, "vin": [ { "gen": { "height": 1041289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc5e8fd2b339941c7d73feb701d5db39215316397e6f0ea62334fdd0fb94e32d" } } ], "extra": [ 1, 61, 156, 155, 71, 21, 75, 202, 187, 36, 165, 3, 91, 226, 175, 128, 214, 211, 112, 231, 59, 55, 39, 229, 8, 73, 211, 109, 79, 157, 233, 212, 233, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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