Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2686df3a842ceb5ed78fee27bb87b6df8bae7cb66c09cfb15a3b0284c9b58b

Tx prefix hash: ace56273fa9b2b380f16a21026f3b1b4c0dd83179dd96ae8d77d6b1193f3c80b
Tx public key: c70562426509ef7a9620d7696c1ab5af70f2d69d4deeb31ece96eb90b77ce0b8
Timestamp: 1577633170 Timestamp [UCT]: 2019-12-29 15:26:10 Age [y:d:h:m:s]: 05:138:08:14:18
Block: 34397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1248679 RingCT/type: yes/0
Extra: 01c70562426509ef7a9620d7696c1ab5af70f2d69d4deeb31ece96eb90b77ce0b80211000000038a2ee0d9000000000000000000

1 output(s) for total of 472.094907781000 dcy

stealth address amount amount idx
00: d04a50288fe391b560108fe051187153486691968d210fec36ac5d7e9280e3ca 472.094907781000 57891 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": 34407, "vin": [ { "gen": { "height": 34397 } } ], "vout": [ { "amount": 472094907781, "target": { "key": "d04a50288fe391b560108fe051187153486691968d210fec36ac5d7e9280e3ca" } } ], "extra": [ 1, 199, 5, 98, 66, 101, 9, 239, 122, 150, 32, 215, 105, 108, 26, 181, 175, 112, 242, 214, 157, 77, 238, 179, 30, 206, 150, 235, 144, 183, 124, 224, 184, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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