Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdf212548f2269d02cb124b1930e14371d3be7e8226637b5862c9f93ec3b5fef

Tx prefix hash: 953dbe192d9a24b8355700290eb0b4988a49e3a78aa607d83fd08bb28112ada0
Tx public key: ac880dd7f34dca3f972ce01a0a3c8808933e45cc3b3f87a1b532dd301d01edd5
Timestamp: 1704789326 Timestamp [UCT]: 2024-01-09 08:35:26 Age [y:d:h:m:s]: 01:303:13:50:19
Block: 931438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475796 RingCT/type: yes/0
Extra: 01ac880dd7f34dca3f972ce01a0a3c8808933e45cc3b3f87a1b532dd301d01edd502110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0342dc2973852a0414bee23ee209f4439b0f67a565796303d510ea5e0de4f947 0.600000000000 1389336 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": 931448, "vin": [ { "gen": { "height": 931438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0342dc2973852a0414bee23ee209f4439b0f67a565796303d510ea5e0de4f947" } } ], "extra": [ 1, 172, 136, 13, 215, 243, 77, 202, 63, 151, 44, 224, 26, 10, 60, 136, 8, 147, 62, 69, 204, 59, 63, 135, 161, 181, 50, 221, 48, 29, 1, 237, 213, 2, 17, 0, 0, 0, 11, 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