Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d23006ff13cb2604cea6491cba01a8877980f5b6e5489764f09d3fc5163c12e

Tx prefix hash: 6970c494d376ffc3d886a2341ba6420b131473a129fbb1c2d519a9b1fccd588b
Tx public key: e043f9ebab0f9021731078828dfb9a9723a2e8d31d289aa67d220b8becd0d8ab
Timestamp: 1735919928 Timestamp [UCT]: 2025-01-03 15:58:48 Age [y:d:h:m:s]: 00:097:14:00:58
Block: 1189412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69531 RingCT/type: yes/0
Extra: 01e043f9ebab0f9021731078828dfb9a9723a2e8d31d289aa67d220b8becd0d8ab0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c71acc2ef9e1d88c1ab16b5030f266353d422f41276717575468396268a5387c 0.600000000000 1675921 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": 1189422, "vin": [ { "gen": { "height": 1189412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c71acc2ef9e1d88c1ab16b5030f266353d422f41276717575468396268a5387c" } } ], "extra": [ 1, 224, 67, 249, 235, 171, 15, 144, 33, 115, 16, 120, 130, 141, 251, 154, 151, 35, 162, 232, 211, 29, 40, 154, 166, 125, 34, 11, 139, 236, 208, 216, 171, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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