Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e06c2458c7191dc4b4113d161e319b1e50f5e0e7f53e13e262b988719c7d995

Tx prefix hash: 18b800fd25567265ca69303de45807a0b8bb46a4be9bc2a2b6073db11e6ad09a
Tx public key: aad182879c47bc57396b6670f978bcb10f41082ba11b580297092f2ed764925d
Timestamp: 1703309144 Timestamp [UCT]: 2023-12-23 05:25:44 Age [y:d:h:m:s]: 02:013:00:48:00
Block: 919181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529105 RingCT/type: yes/0
Extra: 01aad182879c47bc57396b6670f978bcb10f41082ba11b580297092f2ed764925d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56184843c6aa1ac7b2e29fd8a0f3e4682a3fac052ea9cbc274d6c2e95cdc30cc 0.600000000000 1376847 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": 919191, "vin": [ { "gen": { "height": 919181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56184843c6aa1ac7b2e29fd8a0f3e4682a3fac052ea9cbc274d6c2e95cdc30cc" } } ], "extra": [ 1, 170, 209, 130, 135, 156, 71, 188, 87, 57, 107, 102, 112, 249, 120, 188, 177, 15, 65, 8, 43, 161, 27, 88, 2, 151, 9, 47, 46, 215, 100, 146, 93, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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