Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86cab66929b4bfc78cf5042ecf31ae4d719f28f232b886d217df73062172eb40

Tx prefix hash: feed62586248dfbbcf5b1f488e2b7529200e08e71b2d7b4d29347a6277673177
Tx public key: 43a54ea03629b1579bb2e4e2fd5aa34eb029753ae5e7bd068d9c06ca1bb727fc
Timestamp: 1722755384 Timestamp [UCT]: 2024-08-04 07:09:44 Age [y:d:h:m:s]: 00:257:02:11:03
Block: 1080394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183652 RingCT/type: yes/0
Extra: 0143a54ea03629b1579bb2e4e2fd5aa34eb029753ae5e7bd068d9c06ca1bb727fc021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e14c7655583f88240eac5590572f43f164f49667aae3c2eff9d09678a92ed0a9 0.600000000000 1553733 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": 1080404, "vin": [ { "gen": { "height": 1080394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e14c7655583f88240eac5590572f43f164f49667aae3c2eff9d09678a92ed0a9" } } ], "extra": [ 1, 67, 165, 78, 160, 54, 41, 177, 87, 155, 178, 228, 226, 253, 90, 163, 78, 176, 41, 117, 58, 229, 231, 189, 6, 141, 156, 6, 202, 27, 183, 39, 252, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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