Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6194a7294fca4f46f10467a13b4aa2c621475277f9248fa1ab2a0f13f150c73

Tx prefix hash: 97f716a73e17f97dbf7fd02617e8a162f650dff03ac2698b1a9c345e1d8fcd9d
Tx public key: 6fe5f79e50228a8e7bc32cbe64215f0310a2a997490cf6966daab19788a049d9
Timestamp: 1705068646 Timestamp [UCT]: 2024-01-12 14:10:46 Age [y:d:h:m:s]: 01:301:06:28:23
Block: 933758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474127 RingCT/type: yes/0
Extra: 016fe5f79e50228a8e7bc32cbe64215f0310a2a997490cf6966daab19788a049d9021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f7e1bc43a209351f137f1b0e6899f38960d38c229a7f4919ad08c433471f9b1 0.600000000000 1391732 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": 933768, "vin": [ { "gen": { "height": 933758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f7e1bc43a209351f137f1b0e6899f38960d38c229a7f4919ad08c433471f9b1" } } ], "extra": [ 1, 111, 229, 247, 158, 80, 34, 138, 142, 123, 195, 44, 190, 100, 33, 95, 3, 16, 162, 169, 151, 73, 12, 246, 150, 109, 170, 177, 151, 136, 160, 73, 217, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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