Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35b1be2e2555c7a549572acc5ab6780a52f5c65b5e9139230c80d9732ebf42a5

Tx prefix hash: 6ad58770f731fb423595aefcf7938919068740320334c244bf67da5d1aa9a7dd
Tx public key: 8f3879532b330e1510ebfce21a1546437ee66eaa6745f9c71a7f500f55c1414e
Timestamp: 1700816875 Timestamp [UCT]: 2023-11-24 09:07:55 Age [y:d:h:m:s]: 01:186:17:14:47
Block: 898516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394660 RingCT/type: yes/0
Extra: 018f3879532b330e1510ebfce21a1546437ee66eaa6745f9c71a7f500f55c1414e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.646909436000 dcy

stealth address amount amount idx
00: 2f118a508eb897e3f0612bf0d8c697d8956d538308d5ea22d7e262a114daf5cc 0.646909436000 1354937 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": 898526, "vin": [ { "gen": { "height": 898516 } } ], "vout": [ { "amount": 646909436, "target": { "key": "2f118a508eb897e3f0612bf0d8c697d8956d538308d5ea22d7e262a114daf5cc" } } ], "extra": [ 1, 143, 56, 121, 83, 43, 51, 14, 21, 16, 235, 252, 226, 26, 21, 70, 67, 126, 230, 110, 170, 103, 69, 249, 199, 26, 127, 80, 15, 85, 193, 65, 78, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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