Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c896e68dc1324f911d303f114259c95de7d241c08b6f84b13ff33a35fcb38ac

Tx prefix hash: e88f0c268686969da77bf342e8ba0380e68e5968a73b78aa89a2f44f73c91001
Tx public key: c8d6652d8928e966398a45a4229b514696848ce7c292979050c2bf5635e6ca2e
Timestamp: 1709080258 Timestamp [UCT]: 2024-02-28 00:30:58 Age [y:d:h:m:s]: 01:339:11:55:13
Block: 967034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501285 RingCT/type: yes/0
Extra: 01c8d6652d8928e966398a45a4229b514696848ce7c292979050c2bf5635e6ca2e02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7ed05a1b7cd3989e1d48cd838496ff0262222ccc0e80d9febe3d6b23845b215 0.600000000000 1426805 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": 967044, "vin": [ { "gen": { "height": 967034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7ed05a1b7cd3989e1d48cd838496ff0262222ccc0e80d9febe3d6b23845b215" } } ], "extra": [ 1, 200, 214, 101, 45, 137, 40, 233, 102, 57, 138, 69, 164, 34, 155, 81, 70, 150, 132, 140, 231, 194, 146, 151, 144, 80, 194, 191, 86, 53, 230, 202, 46, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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