Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65857db278169d8485ace4722c8f8721a0f39ebfff945ede16feae27d1ec1a97

Tx prefix hash: 3ad03f814bd97ef7929eb33fbc560b886ac1bc9b969a998cb669b1a13e71b7e6
Tx public key: cf50462a8da1c1553436c599a33cc84cc31d9081ba8775dbef782ae79b6e2bc8
Timestamp: 1722486763 Timestamp [UCT]: 2024-08-01 04:32:43 Age [y:d:h:m:s]: 00:288:19:41:53
Block: 1078161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206357 RingCT/type: yes/0
Extra: 01cf50462a8da1c1553436c599a33cc84cc31d9081ba8775dbef782ae79b6e2bc8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c80d716611813063d50def0c29302f77885e5c024d6c4af0c4c0e8b6e8aa07d 0.600000000000 1550728 of 15

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": 1078171, "vin": [ { "gen": { "height": 1078161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c80d716611813063d50def0c29302f77885e5c024d6c4af0c4c0e8b6e8aa07d" } } ], "extra": [ 1, 207, 80, 70, 42, 141, 161, 193, 85, 52, 54, 197, 153, 163, 60, 200, 76, 195, 29, 144, 129, 186, 135, 117, 219, 239, 120, 42, 231, 155, 110, 43, 200, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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