Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22113c06614ec4091a4c0c23369c2d907cf110f8ae4fee55b7be56106ffa6c82

Tx prefix hash: 23ef99852e323c8de451660cd6b40359acf250f00484acbe48c8d2f73245fe7f
Tx public key: cd164accd183af4b8b548526e5bc4d20ab5a3e5c16005aea0c902901626cc5bc
Timestamp: 1714343455 Timestamp [UCT]: 2024-04-28 22:30:55 Age [y:d:h:m:s]: 00:325:10:57:38
Block: 1010649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232681 RingCT/type: yes/0
Extra: 01cd164accd183af4b8b548526e5bc4d20ab5a3e5c16005aea0c902901626cc5bc02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60271f4753f6163f5f83b4beb51d457d89c77d9a426730a8c9f4898c7eb7878d 0.600000000000 1472667 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": 1010659, "vin": [ { "gen": { "height": 1010649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60271f4753f6163f5f83b4beb51d457d89c77d9a426730a8c9f4898c7eb7878d" } } ], "extra": [ 1, 205, 22, 74, 204, 209, 131, 175, 75, 139, 84, 133, 38, 229, 188, 77, 32, 171, 90, 62, 92, 22, 0, 90, 234, 12, 144, 41, 1, 98, 108, 197, 188, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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