Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abef4ea0df539a437cb9039a347a4b3d39b585425fb2178f2138992a460d072a

Tx prefix hash: 92e39236c8b5fccbce5203b486453427a4e8ffdb14fa39a2fa7c2a68b572638a
Tx public key: 8cffd381f3569ef1eae2273dd79f8ec6e20530b5a861b9416b6128b7bfde0a92
Timestamp: 1740840852 Timestamp [UCT]: 2025-03-01 14:54:12 Age [y:d:h:m:s]: 00:259:11:33:58
Block: 1229874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183205 RingCT/type: yes/0
Extra: 018cffd381f3569ef1eae2273dd79f8ec6e20530b5a861b9416b6128b7bfde0a92021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0322265f35f48a0e5d7e34424e948e9b19c56442a5d2830520b9354c025d16bf 0.600000000000 1716765 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": 1229884, "vin": [ { "gen": { "height": 1229874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0322265f35f48a0e5d7e34424e948e9b19c56442a5d2830520b9354c025d16bf" } } ], "extra": [ 1, 140, 255, 211, 129, 243, 86, 158, 241, 234, 226, 39, 61, 215, 159, 142, 198, 226, 5, 48, 181, 168, 97, 185, 65, 107, 97, 40, 183, 191, 222, 10, 146, 2, 17, 0, 0, 0, 6, 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