Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd1ae21bcd20eb3e2e586fa848086fe06c0f0e8cf678c11f0e52e0899b90fbb3

Tx prefix hash: f560678c78655081e0d2b2f0430e6a21543730e0fc276f69905ad9d8b70ebf31
Tx public key: 0fd01514c09abca543804e6686908f99d8eca21e881b6c41318cabc0e636ad0d
Timestamp: 1730574032 Timestamp [UCT]: 2024-11-02 19:00:32 Age [y:d:h:m:s]: 00:081:09:07:57
Block: 1145134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58182 RingCT/type: yes/0
Extra: 010fd01514c09abca543804e6686908f99d8eca21e881b6c41318cabc0e636ad0d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 727054c2c551c7c53ebc6130578b74e7b06730ea7e4e71d5036723d19dab9b1a 0.600000000000 1629529 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": 1145144, "vin": [ { "gen": { "height": 1145134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "727054c2c551c7c53ebc6130578b74e7b06730ea7e4e71d5036723d19dab9b1a" } } ], "extra": [ 1, 15, 208, 21, 20, 192, 154, 188, 165, 67, 128, 78, 102, 134, 144, 143, 153, 216, 236, 162, 30, 136, 27, 108, 65, 49, 140, 171, 192, 230, 54, 173, 13, 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