Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64ebcddff7d0f5c48a248293f7b934411cd424878b505d82bb78f3309f2ceaac

Tx prefix hash: bf02af534caad4739c37fc59d5961183b1afa1cc7ee824157faddd97dcc0662a
Tx public key: a76c5ac8303302ae4cdfa4d6f67df0d8d91f7ca58b4a30796a9d6a95dcaaebcc
Timestamp: 1681680469 Timestamp [UCT]: 2023-04-16 21:27:49 Age [y:d:h:m:s]: 02:001:10:35:05
Block: 740105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523180 RingCT/type: yes/0
Extra: 01a76c5ac8303302ae4cdfa4d6f67df0d8d91f7ca58b4a30796a9d6a95dcaaebcc021100000003faf35c9c000000000000000000

1 output(s) for total of 2.166332526000 dcy

stealth address amount amount idx
00: fe992c484f4c2ba754e0ea23d7326b0d15df43e60ec3d11054d2452dea92d06e 2.166332526000 1186986 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": 740115, "vin": [ { "gen": { "height": 740105 } } ], "vout": [ { "amount": 2166332526, "target": { "key": "fe992c484f4c2ba754e0ea23d7326b0d15df43e60ec3d11054d2452dea92d06e" } } ], "extra": [ 1, 167, 108, 90, 200, 48, 51, 2, 174, 76, 223, 164, 214, 246, 125, 240, 216, 217, 31, 124, 165, 139, 74, 48, 121, 106, 157, 106, 149, 220, 170, 235, 204, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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