Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 072a03578d3740dba9990f06beddf19192c29334641c6011976f63326d68b7fa

Tx prefix hash: 7cb893ed9fd948af415b3d5e2ccf7c0f2692524dc4bb9fb8a267bc4d1b40b589
Tx public key: 2763403f04a1e4747167b8528bddb18b7380df58f52e3b0a92f85c654231b5aa
Timestamp: 1705468385 Timestamp [UCT]: 2024-01-17 05:13:05 Age [y:d:h:m:s]: 01:296:18:37:24
Block: 937051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470937 RingCT/type: yes/0
Extra: 012763403f04a1e4747167b8528bddb18b7380df58f52e3b0a92f85c654231b5aa0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1348f7d128be4a7d2760b3440cb5351f7bf88d153b6d344f8040ce334e82617b 0.600000000000 1395095 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": 937061, "vin": [ { "gen": { "height": 937051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1348f7d128be4a7d2760b3440cb5351f7bf88d153b6d344f8040ce334e82617b" } } ], "extra": [ 1, 39, 99, 64, 63, 4, 161, 228, 116, 113, 103, 184, 82, 139, 221, 177, 139, 115, 128, 223, 88, 245, 46, 59, 10, 146, 248, 92, 101, 66, 49, 181, 170, 2, 17, 0, 0, 0, 3, 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