Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 706b871b5ac2be549844c944b4e51ac67dca70d98b7c04b56f18e84bf33e7871

Tx prefix hash: 585a9596b2558121cda9461cde0e0edb3ff60f080f323e6a573eac6a40c2c2ef
Tx public key: 5cf0e5c8eba8bc8b1410d9fc5ce74eea96ed4bb22d48d4239dc4f57433fd9d98
Timestamp: 1708325673 Timestamp [UCT]: 2024-02-19 06:54:33 Age [y:d:h:m:s]: 01:059:17:35:55
Block: 960765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303736 RingCT/type: yes/0
Extra: 015cf0e5c8eba8bc8b1410d9fc5ce74eea96ed4bb22d48d4239dc4f57433fd9d9802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a650f767dbadfe29adb3f4116561e92602a2032fd8dcb9f0fd9dfd43c2c6a94 0.600000000000 1420352 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": 960775, "vin": [ { "gen": { "height": 960765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a650f767dbadfe29adb3f4116561e92602a2032fd8dcb9f0fd9dfd43c2c6a94" } } ], "extra": [ 1, 92, 240, 229, 200, 235, 168, 188, 139, 20, 16, 217, 252, 92, 231, 78, 234, 150, 237, 75, 178, 45, 72, 212, 35, 157, 196, 245, 116, 51, 253, 157, 152, 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