Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 071b29aaa7397fa4bd5dc3d5a1abbe314afcb609c884aecfd2ffb817f93de4f5

Tx prefix hash: 2b89549e0c708aaf1a746a0fba1f1460b110db1d6727f13b2f409c6753471585
Tx public key: 0fc2879888abf38af54ec22c27bc282c2518da154c6a105d3ff4e5c2c57dfff1
Timestamp: 1745161918 Timestamp [UCT]: 2025-04-20 15:11:58 Age [y:d:h:m:s]: 00:214:06:48:57
Block: 1265636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150882 RingCT/type: yes/0
Extra: 010fc2879888abf38af54ec22c27bc282c2518da154c6a105d3ff4e5c2c57dfff10211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 213fddce6d8c470158d18408e1c6ebf15f7a0b97066812946a7c8eb200d4ba00 0.600000000000 1752849 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": 1265646, "vin": [ { "gen": { "height": 1265636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "213fddce6d8c470158d18408e1c6ebf15f7a0b97066812946a7c8eb200d4ba00" } } ], "extra": [ 1, 15, 194, 135, 152, 136, 171, 243, 138, 245, 78, 194, 44, 39, 188, 40, 44, 37, 24, 218, 21, 76, 106, 16, 93, 63, 244, 229, 194, 197, 125, 255, 241, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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