Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb23fbe4fdf00b4a4a2101d79de0bc67112051cd3027481fbe64e4c318207d21

Tx prefix hash: 2c75965c6bade96b4a0bbbe64fc1037a9fe58e7b8bc707a810e76bfcda9179b0
Tx public key: c1bcac1deb2f958ce46414cfe0e2de413869f05fea43f216093812dc984a0bf2
Timestamp: 1670994935 Timestamp [UCT]: 2022-12-14 05:15:35 Age [y:d:h:m:s]: 02:117:15:07:50
Block: 652178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 605746 RingCT/type: yes/0
Extra: 01c1bcac1deb2f958ce46414cfe0e2de413869f05fea43f216093812dc984a0bf20211000000047e406890000000000000000000

1 output(s) for total of 4.237049496000 dcy

stealth address amount amount idx
00: 789a739169c521379e17ec2c6dba5004e897601f8c13b38fd65a5d5fd34b0c31 4.237049496000 1092601 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": 652188, "vin": [ { "gen": { "height": 652178 } } ], "vout": [ { "amount": 4237049496, "target": { "key": "789a739169c521379e17ec2c6dba5004e897601f8c13b38fd65a5d5fd34b0c31" } } ], "extra": [ 1, 193, 188, 172, 29, 235, 47, 149, 140, 228, 100, 20, 207, 224, 226, 222, 65, 56, 105, 240, 95, 234, 67, 242, 22, 9, 56, 18, 220, 152, 74, 11, 242, 2, 17, 0, 0, 0, 4, 126, 64, 104, 144, 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