Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e051bc67ab7d63e396faefcb1c15e8f5bd50b972ee98657f80b94b3bea2b149

Tx prefix hash: e15e0a2062bbda27927dd58a7269f4ffa507d46bf0e25d7e2def94758b7b6b7b
Tx public key: 572bae27dfd28a59a5f386b0d69dfbe8278c8c7e7822cf6e1ce813ecd7fb86f0
Timestamp: 1735050398 Timestamp [UCT]: 2024-12-24 14:26:38 Age [y:d:h:m:s]: 00:101:14:34:00
Block: 1182223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72386 RingCT/type: yes/0
Extra: 01572bae27dfd28a59a5f386b0d69dfbe8278c8c7e7822cf6e1ce813ecd7fb86f0021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21774f7edc21faf4d96ec06d4372283064a831a674c1f3621ee8815891f5cc4f 0.600000000000 1668656 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": 1182233, "vin": [ { "gen": { "height": 1182223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21774f7edc21faf4d96ec06d4372283064a831a674c1f3621ee8815891f5cc4f" } } ], "extra": [ 1, 87, 43, 174, 39, 223, 210, 138, 89, 165, 243, 134, 176, 214, 157, 251, 232, 39, 140, 140, 126, 120, 34, 207, 110, 28, 232, 19, 236, 215, 251, 134, 240, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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