Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8443a08640903ea3fdc6f6aedbf3ce7ed76046a9c849097c11aa2a1ea8f23fd

Tx prefix hash: e56888190c5e9e5737f44a2bcc2568313b34bb63a1a68977ce21442f3bd61abf
Tx public key: e5b0566cae0c4124be93f1682ffc10dec69ad25213e8462f1ddac9bce6a356bb
Timestamp: 1706067658 Timestamp [UCT]: 2024-01-24 03:40:58 Age [y:d:h:m:s]: 01:150:21:15:24
Block: 942017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368789 RingCT/type: yes/0
Extra: 01e5b0566cae0c4124be93f1682ffc10dec69ad25213e8462f1ddac9bce6a356bb02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ff96a4280722f7030ba2b4f65c07a3d17c0374cc97140475c90c0ef3c0f89d7 0.600000000000 1400183 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": 942027, "vin": [ { "gen": { "height": 942017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ff96a4280722f7030ba2b4f65c07a3d17c0374cc97140475c90c0ef3c0f89d7" } } ], "extra": [ 1, 229, 176, 86, 108, 174, 12, 65, 36, 190, 147, 241, 104, 47, 252, 16, 222, 198, 154, 210, 82, 19, 232, 70, 47, 29, 218, 201, 188, 230, 163, 86, 187, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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