Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e868d95187e88c896d9508c1a0b298a8cf97864341a2ab201f00cb3798bfc25d

Tx prefix hash: 4e5dfbf63005505788e2ae06b5b4c0b67602c1e84a95c0f3ff37e5e6fe2431b2
Tx public key: a4de58d681279940bf9b4425f8dbea099a992c32609cd88dd3fc1b98d439e0ce
Timestamp: 1711883028 Timestamp [UCT]: 2024-03-31 11:03:48 Age [y:d:h:m:s]: 01:008:02:32:01
Block: 990276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266734 RingCT/type: yes/0
Extra: 01a4de58d681279940bf9b4425f8dbea099a992c32609cd88dd3fc1b98d439e0ce02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 925ea999d6a7525d2b6936d563d0ba63fb6550afda339f199e3c7415962277a3 0.600000000000 1450598 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": 990286, "vin": [ { "gen": { "height": 990276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "925ea999d6a7525d2b6936d563d0ba63fb6550afda339f199e3c7415962277a3" } } ], "extra": [ 1, 164, 222, 88, 214, 129, 39, 153, 64, 191, 155, 68, 37, 248, 219, 234, 9, 154, 153, 44, 50, 96, 156, 216, 141, 211, 252, 27, 152, 212, 57, 224, 206, 2, 17, 0, 0, 0, 5, 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