Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd0944ff3a08fd76eb403d636abe83b0614ef373f7f656179ed9f56a143767cc

Tx prefix hash: c3895740ce80900d4178ae45b665056b9fb32f9f065c8605d623d0c1bbdb3a97
Tx public key: 0ba971deb5a3c5cef1ac2019efde6ab10662dad5d2e17d618fb6a4fe6d865a37
Timestamp: 1681603482 Timestamp [UCT]: 2023-04-16 00:04:42 Age [y:d:h:m:s]: 02:039:02:47:01
Block: 739466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550149 RingCT/type: yes/0
Extra: 010ba971deb5a3c5cef1ac2019efde6ab10662dad5d2e17d618fb6a4fe6d865a3702110000000375e3f0e9000000000000000000

1 output(s) for total of 2.176919620000 dcy

stealth address amount amount idx
00: 7a1437ecd6e9632f610e283d81e8f77b9737f9a55665ab927821c37e62f557ee 2.176919620000 1186317 of 0

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": 739476, "vin": [ { "gen": { "height": 739466 } } ], "vout": [ { "amount": 2176919620, "target": { "key": "7a1437ecd6e9632f610e283d81e8f77b9737f9a55665ab927821c37e62f557ee" } } ], "extra": [ 1, 11, 169, 113, 222, 181, 163, 197, 206, 241, 172, 32, 25, 239, 222, 106, 177, 6, 98, 218, 213, 210, 225, 125, 97, 143, 182, 164, 254, 109, 134, 90, 55, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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