Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9166bcf9a5d831b8be5a62939f44069d52100c37dbfcf782061ad20acd8b3c2d

Tx prefix hash: f3ca9cb96329bc4b4916dd0e5e414347da25e76ba19f1d286d02964dff281faf
Tx public key: 50f267db2ae53e596b9d485838a0479e0123d420dd1c8a551b5eaedbe9f24329
Timestamp: 1708617937 Timestamp [UCT]: 2024-02-22 16:05:37 Age [y:d:h:m:s]: 01:117:20:01:50
Block: 963189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345143 RingCT/type: yes/0
Extra: 0150f267db2ae53e596b9d485838a0479e0123d420dd1c8a551b5eaedbe9f243290211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f282c9887c7a8e90edaefc4516047d27af0a185e1a7ce1576c92a0a6cb1b247 0.600000000000 1422888 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": 963199, "vin": [ { "gen": { "height": 963189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f282c9887c7a8e90edaefc4516047d27af0a185e1a7ce1576c92a0a6cb1b247" } } ], "extra": [ 1, 80, 242, 103, 219, 42, 229, 62, 89, 107, 157, 72, 88, 56, 160, 71, 158, 1, 35, 212, 32, 221, 28, 138, 85, 27, 94, 174, 219, 233, 242, 67, 41, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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