Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af6e44c44913fa24ad656cc2f9e67540ba51cb68fb89f65cb7c7d80a335a2715

Tx prefix hash: 5ebb48c4844bc50fca92555d0aa741bd5a8443a3d3df5e9917a67075445c91f0
Tx public key: c9eaa97336a5e84a9ae3c4ae35c39c1889716b9b9228f2e409a0ac1a092bb983
Timestamp: 1687491366 Timestamp [UCT]: 2023-06-23 03:36:06 Age [y:d:h:m:s]: 01:294:15:46:23
Block: 788290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471761 RingCT/type: yes/0
Extra: 01c9eaa97336a5e84a9ae3c4ae35c39c1889716b9b9228f2e409a0ac1a092bb983021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.499920160000 dcy

stealth address amount amount idx
00: 88b720486148aa4fc71655e12e1de811d6a9776b3c1468c73ece28ebdaff014d 1.499920160000 1238391 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": 788300, "vin": [ { "gen": { "height": 788290 } } ], "vout": [ { "amount": 1499920160, "target": { "key": "88b720486148aa4fc71655e12e1de811d6a9776b3c1468c73ece28ebdaff014d" } } ], "extra": [ 1, 201, 234, 169, 115, 54, 165, 232, 74, 154, 227, 196, 174, 53, 195, 156, 24, 137, 113, 107, 155, 146, 40, 242, 228, 9, 160, 172, 26, 9, 43, 185, 131, 2, 17, 0, 0, 0, 4, 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