Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105eaa94e62d9a607f3e54ecc0a383095bd692a30670b8143a124541f9854a51

Tx prefix hash: 5db82459b6da8e02bd52bcb58b3024e604f2f29641299a07f8a0e358c1f751d2
Tx public key: 526d2e9cda708c616a3a3bbdb7155b278de883e030901736dcbacdc6692f78c0
Timestamp: 1718046501 Timestamp [UCT]: 2024-06-10 19:08:21 Age [y:d:h:m:s]: 00:256:20:00:08
Block: 1041361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183491 RingCT/type: yes/0
Extra: 01526d2e9cda708c616a3a3bbdb7155b278de883e030901736dcbacdc6692f78c002110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afc5943a28abfc66b5d5b917d790a1192700bda33d2aed193c52b2c9d9f47ceb 0.600000000000 1510026 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": 1041371, "vin": [ { "gen": { "height": 1041361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afc5943a28abfc66b5d5b917d790a1192700bda33d2aed193c52b2c9d9f47ceb" } } ], "extra": [ 1, 82, 109, 46, 156, 218, 112, 140, 97, 106, 58, 59, 189, 183, 21, 91, 39, 141, 232, 131, 224, 48, 144, 23, 54, 220, 186, 205, 198, 105, 47, 120, 192, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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