Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: becc912bfd50e7cf077b2572b770104af68be1a9b728c135da9a2e0510eaa5b9

Tx prefix hash: 73f9f0c6edbc225dcf826f41a32a1e6a91c1dfb3ae1e38bcda124a648810899c
Tx public key: 826d7a14baf23e70a973157a3fa9e4862d3a79d88d65e84968541794e0f76541
Timestamp: 1745896216 Timestamp [UCT]: 2025-04-29 03:10:16 Age [y:d:h:m:s]: 00:195:04:27:23
Block: 1271737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137200 RingCT/type: yes/0
Extra: 01826d7a14baf23e70a973157a3fa9e4862d3a79d88d65e84968541794e0f7654102110000000725a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4491df2f8f02fbe9f845a4246210e93026e4a24740767372701d568df501a4de 0.600000000000 1759004 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": 1271747, "vin": [ { "gen": { "height": 1271737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4491df2f8f02fbe9f845a4246210e93026e4a24740767372701d568df501a4de" } } ], "extra": [ 1, 130, 109, 122, 20, 186, 242, 62, 112, 169, 115, 21, 122, 63, 169, 228, 134, 45, 58, 121, 216, 141, 101, 232, 73, 104, 84, 23, 148, 224, 247, 101, 65, 2, 17, 0, 0, 0, 7, 37, 163, 90, 15, 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