Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 504a4c2a4e8f28d206a0cd2afad691c544f63120fb2e6237e4f5f65f4b917482

Tx prefix hash: ee7d1ee85eefdf1c1509831ce1f6a1906a8f06831cc48496cf537857a5e16f89
Tx public key: 37d288642ac1f685e5dd50041e0acb788dfa1bbc61d39db019041d18dcddf2d4
Timestamp: 1720068626 Timestamp [UCT]: 2024-07-04 04:50:26 Age [y:d:h:m:s]: 00:281:03:50:19
Block: 1058115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200904 RingCT/type: yes/0
Extra: 0137d288642ac1f685e5dd50041e0acb788dfa1bbc61d39db019041d18dcddf2d40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bfbab34fbfbec9ef3a9c3e02a831b6e4a60eb2255d41d8bdcc097e42f67f231 0.600000000000 1528564 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": 1058125, "vin": [ { "gen": { "height": 1058115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bfbab34fbfbec9ef3a9c3e02a831b6e4a60eb2255d41d8bdcc097e42f67f231" } } ], "extra": [ 1, 55, 210, 136, 100, 42, 193, 246, 133, 229, 221, 80, 4, 30, 10, 203, 120, 141, 250, 27, 188, 97, 211, 157, 176, 25, 4, 29, 24, 220, 221, 242, 212, 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