Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5e7514b9f2d46f5fde89b1a78b9ca1f300fb406f710dba6ae862f3987fa90d8

Tx prefix hash: 6995877fb3f234d07c46ec7afe4094fadb76a786cb93f0ad8d0a5e6c99b0763d
Tx public key: aa2d449e67034bbdbbb45c2d6aa2762113acc6e2b4e440c706c14bc98db3af66
Timestamp: 1707643123 Timestamp [UCT]: 2024-02-11 09:18:43 Age [y:d:h:m:s]: 00:221:07:01:36
Block: 955102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158522 RingCT/type: yes/0
Extra: 01aa2d449e67034bbdbbb45c2d6aa2762113acc6e2b4e440c706c14bc98db3af6602110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dac930a5d47b63195da0ef9229d530c25bbb79e4da9eec71d8942c4a7a13c7f 0.600000000000 1414386 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": 955112, "vin": [ { "gen": { "height": 955102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dac930a5d47b63195da0ef9229d530c25bbb79e4da9eec71d8942c4a7a13c7f" } } ], "extra": [ 1, 170, 45, 68, 158, 103, 3, 75, 189, 187, 180, 92, 45, 106, 162, 118, 33, 19, 172, 198, 226, 180, 228, 64, 199, 6, 193, 75, 201, 141, 179, 175, 102, 2, 17, 0, 0, 0, 10, 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