Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ace877db911c3c6dfd98d20563fa64643a1afb1ec6d5beb4994c54c90180752d

Tx prefix hash: 240db8e356b3e8af1db3e493a6ada4473021925558a2383b67a3464326c72205
Tx public key: 75319661a5b64a8d51fadfea0d7e3c4866db326557e5ccf01faa8b1dc100a805
Timestamp: 1685862064 Timestamp [UCT]: 2023-06-04 07:01:04 Age [y:d:h:m:s]: 01:354:10:54:29
Block: 774779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514565 RingCT/type: yes/0
Extra: 0175319661a5b64a8d51fadfea0d7e3c4866db326557e5ccf01faa8b1dc100a805021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.662783529000 dcy

stealth address amount amount idx
00: a1e2e680078139e0200637a08532b899682165e1c59d28c8562eca2a7eb333e4 1.662783529000 1224266 of 0

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": 774789, "vin": [ { "gen": { "height": 774779 } } ], "vout": [ { "amount": 1662783529, "target": { "key": "a1e2e680078139e0200637a08532b899682165e1c59d28c8562eca2a7eb333e4" } } ], "extra": [ 1, 117, 49, 150, 97, 165, 182, 74, 141, 81, 250, 223, 234, 13, 126, 60, 72, 102, 219, 50, 101, 87, 229, 204, 240, 31, 170, 139, 29, 193, 0, 168, 5, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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