Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 071cb2b586c922c67ce74588a58d046491ef5f73164d21568ac642f706e770fe

Tx prefix hash: c66f900a6f7e589389a39252099d051a9eff364cf2f587edc0a4d9da732d99bf
Tx public key: ded9b45ecdc8cee7db0fa2c40e31ab354d41a937db7c4379a1f1a56ed0538414
Timestamp: 1715735809 Timestamp [UCT]: 2024-05-15 01:16:49 Age [y:d:h:m:s]: 01:002:01:28:46
Block: 1022203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262391 RingCT/type: yes/0
Extra: 01ded9b45ecdc8cee7db0fa2c40e31ab354d41a937db7c4379a1f1a56ed0538414021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b49ebc6e0994ffd54f7fe7755e395be3744b3eaa7271c5ec49c2271ed9a5ff7 0.600000000000 1486736 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": 1022213, "vin": [ { "gen": { "height": 1022203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b49ebc6e0994ffd54f7fe7755e395be3744b3eaa7271c5ec49c2271ed9a5ff7" } } ], "extra": [ 1, 222, 217, 180, 94, 205, 200, 206, 231, 219, 15, 162, 196, 14, 49, 171, 53, 77, 65, 169, 55, 219, 124, 67, 121, 161, 241, 165, 110, 208, 83, 132, 20, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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