Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef8515302bde2a0c6355afd5c3b905c9a645c9a5596b85ebf0db1f669e261e3b

Tx prefix hash: fd75d49fd567373dd56310a93cf2a2439ad3da263c2440c819f83ea6139402c5
Tx public key: acb359d983725653c217f69d0ba520414c4d57147da51adca8ddc9b637212f2a
Timestamp: 1724683073 Timestamp [UCT]: 2024-08-26 14:37:53 Age [y:d:h:m:s]: 00:222:01:36:23
Block: 1096376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158575 RingCT/type: yes/0
Extra: 01acb359d983725653c217f69d0ba520414c4d57147da51adca8ddc9b637212f2a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6369771c1a947e2e5f2c6eefc23d854368a75f0ce606bfb138a63be96132a8f 0.600000000000 1571565 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": 1096386, "vin": [ { "gen": { "height": 1096376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6369771c1a947e2e5f2c6eefc23d854368a75f0ce606bfb138a63be96132a8f" } } ], "extra": [ 1, 172, 179, 89, 217, 131, 114, 86, 83, 194, 23, 246, 157, 11, 165, 32, 65, 76, 77, 87, 20, 125, 165, 26, 220, 168, 221, 201, 182, 55, 33, 47, 42, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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