Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 960f66d123e4b9a06a969ee9c014a12cf51a60ba4f7d7d5683e8abd98a045444

Tx prefix hash: 3cdd476f78753f21a54b76f34b84f43c7334d1a43bb78c0f087fb6e7430b1a3b
Tx public key: a2db44e1eb533730e8c9a313f81a35e34f846f56ca36d4531ba5e4e34a942010
Timestamp: 1717903391 Timestamp [UCT]: 2024-06-09 03:23:11 Age [y:d:h:m:s]: 00:280:06:18:30
Block: 1040172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200298 RingCT/type: yes/0
Extra: 01a2db44e1eb533730e8c9a313f81a35e34f846f56ca36d4531ba5e4e34a9420100211000000020bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b10e03d910df04ed4297ed3824032e4b88b6cde677f8f9a7f1df29b8f0380ba 0.600000000000 1508829 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": 1040182, "vin": [ { "gen": { "height": 1040172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b10e03d910df04ed4297ed3824032e4b88b6cde677f8f9a7f1df29b8f0380ba" } } ], "extra": [ 1, 162, 219, 68, 225, 235, 83, 55, 48, 232, 201, 163, 19, 248, 26, 53, 227, 79, 132, 111, 86, 202, 54, 212, 83, 27, 165, 228, 227, 74, 148, 32, 16, 2, 17, 0, 0, 0, 2, 11, 186, 22, 215, 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