Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63576c56ce6911416595c8d7397031c36486c1dc63788dfbf2183b3f097e83af

Tx prefix hash: 4a5cd2f02e52c76986e2cb77f44e53aa5c9d4241490d4ba95300d8d82c64d169
Tx public key: 5fdd3f8d8b7fbce66c0ad90ed05c0a4620f536cd9d4ae6febb6b7ad8c409660d
Timestamp: 1712317541 Timestamp [UCT]: 2024-04-05 11:45:41 Age [y:d:h:m:s]: 01:042:06:03:48
Block: 993839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291205 RingCT/type: yes/0
Extra: 015fdd3f8d8b7fbce66c0ad90ed05c0a4620f536cd9d4ae6febb6b7ad8c409660d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdec4045fcff9907a209ef8b3ca1d3e48b559e0a3b94631997012d273b93e6f0 0.600000000000 1454227 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": 993849, "vin": [ { "gen": { "height": 993839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdec4045fcff9907a209ef8b3ca1d3e48b559e0a3b94631997012d273b93e6f0" } } ], "extra": [ 1, 95, 221, 63, 141, 139, 127, 188, 230, 108, 10, 217, 14, 208, 92, 10, 70, 32, 245, 54, 205, 157, 74, 230, 254, 187, 107, 122, 216, 196, 9, 102, 13, 2, 17, 0, 0, 0, 6, 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