Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 478fdca2276c5d0634b6ae2bfa1b88e865891d0e30503b83000814636eca047f

Tx prefix hash: 8caa3b1ade57563f5f4b7c04af14694448a30c33f06e573977c21e9ccf8f65fe
Tx public key: 7d50de286cfdc71b8228ea0fd55be359cb9fc364cfd855fa3b7b1e7adce5e7b9
Timestamp: 1708666091 Timestamp [UCT]: 2024-02-23 05:28:11 Age [y:d:h:m:s]: 01:261:23:54:48
Block: 963593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445983 RingCT/type: yes/0
Extra: 017d50de286cfdc71b8228ea0fd55be359cb9fc364cfd855fa3b7b1e7adce5e7b902110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d70d0c1f3a0b55c3dc60828573a1ba02b8edd4fc6d59f4a91576c0340de9c165 0.600000000000 1423308 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": 963603, "vin": [ { "gen": { "height": 963593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d70d0c1f3a0b55c3dc60828573a1ba02b8edd4fc6d59f4a91576c0340de9c165" } } ], "extra": [ 1, 125, 80, 222, 40, 108, 253, 199, 27, 130, 40, 234, 15, 213, 91, 227, 89, 203, 159, 195, 100, 207, 216, 85, 250, 59, 123, 30, 122, 220, 229, 231, 185, 2, 17, 0, 0, 0, 15, 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