Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adc22cd2ef96ca41dadb5664f2a38ccb8f75ccfb2f3d6f314c087bf6659f2564

Tx prefix hash: 55536a7a2ae7f175ef9420db2548f923d59b7019542b83a41e6efdc2ca6d11b3
Tx public key: aac5215ee6dc21d59a695c9cd040cdcf2e5068c6e347748f089feed0d944d422
Timestamp: 1726346723 Timestamp [UCT]: 2024-09-14 20:45:23 Age [y:d:h:m:s]: 01:053:03:32:52
Block: 1110166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296391 RingCT/type: yes/0
Extra: 01aac5215ee6dc21d59a695c9cd040cdcf2e5068c6e347748f089feed0d944d422021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 092f40e204a8c8499c70a06d26e413f748920d8197a70303923bfc1739acb493 0.600000000000 1588679 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": 1110176, "vin": [ { "gen": { "height": 1110166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "092f40e204a8c8499c70a06d26e413f748920d8197a70303923bfc1739acb493" } } ], "extra": [ 1, 170, 197, 33, 94, 230, 220, 33, 213, 154, 105, 92, 156, 208, 64, 205, 207, 46, 80, 104, 198, 227, 71, 116, 143, 8, 159, 238, 208, 217, 68, 212, 34, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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