Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a9af4cd3e09bb4fb9527394297f2b91a337a1737ff8b1e0949b6b8041554cea

Tx prefix hash: 9d743a8fbc52a0560ec49081c09129f10e38d85f440e04e59b3943d69a700aa4
Tx public key: 5d4cd091d6bf88c9d2c13183cc0818c459d3a4f4487e7e96853a25022aa49be0
Timestamp: 1728219183 Timestamp [UCT]: 2024-10-06 12:53:03 Age [y:d:h:m:s]: 00:159:02:44:14
Block: 1125702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113515 RingCT/type: yes/0
Extra: 015d4cd091d6bf88c9d2c13183cc0818c459d3a4f4487e7e96853a25022aa49be002110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6273c536be0951cbc1c16ab02901d055ba8c1494266d3e8f6ebf47a78bb1066c 0.600000000000 1608453 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": 1125712, "vin": [ { "gen": { "height": 1125702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6273c536be0951cbc1c16ab02901d055ba8c1494266d3e8f6ebf47a78bb1066c" } } ], "extra": [ 1, 93, 76, 208, 145, 214, 191, 136, 201, 210, 193, 49, 131, 204, 8, 24, 196, 89, 211, 164, 244, 72, 126, 126, 150, 133, 58, 37, 2, 42, 164, 155, 224, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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