Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7032628cb8cea7218c38de8f89b714097d84cd3f0f337a29e1516061c62a02ce

Tx prefix hash: be37783f9c3293f06bf01853459cd1ccba7821b3d678bc3a7b4a7af60e59833e
Tx public key: af83293e77d16f7fe69368b70311a80b751b380eb9548bf9078bcd752223c376
Timestamp: 1695480827 Timestamp [UCT]: 2023-09-23 14:53:47 Age [y:d:h:m:s]: 01:115:13:47:43
Block: 854479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343882 RingCT/type: yes/0
Extra: 01af83293e77d16f7fe69368b70311a80b751b380eb9548bf9078bcd752223c376021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.905224734000 dcy

stealth address amount amount idx
00: 9e5c4c0bcf5ca66773d07fb897fd9dbaa9225f5279541288f696963e3a0650e8 0.905224734000 1308453 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": 854489, "vin": [ { "gen": { "height": 854479 } } ], "vout": [ { "amount": 905224734, "target": { "key": "9e5c4c0bcf5ca66773d07fb897fd9dbaa9225f5279541288f696963e3a0650e8" } } ], "extra": [ 1, 175, 131, 41, 62, 119, 209, 111, 127, 230, 147, 104, 183, 3, 17, 168, 11, 117, 27, 56, 14, 185, 84, 139, 249, 7, 139, 205, 117, 34, 35, 195, 118, 2, 17, 0, 0, 0, 9, 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