Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d195dca01b50eb9a76bd89dc3fad406b37f23be1b80592bfc2fbf84c4c7a417e

Tx prefix hash: 65244063b5a588ae72f74df66471099d652494c63d3043db64c190dfb64848f0
Tx public key: 4f1a2c913a85e7a329d586e9a7fe05032ac19263708b712ec980cf2c778e52cd
Timestamp: 1763610756 Timestamp [UCT]: 2025-11-20 03:52:36 Age [y:d:h:m:s]: 00:038:14:52:58
Block: 1415980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 27661 RingCT/type: yes/0
Extra: 014f1a2c913a85e7a329d586e9a7fe05032ac19263708b712ec980cf2c778e52cd020844b4064c7db77d34

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5d2be8eabcf0c1c92d1d88d3bdea6e486d6eb9552a32bb7f892c367253bc89e 0.600000000000 1904497 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": 1415990, "vin": [ { "gen": { "height": 1415980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5d2be8eabcf0c1c92d1d88d3bdea6e486d6eb9552a32bb7f892c367253bc89e" } } ], "extra": [ 1, 79, 26, 44, 145, 58, 133, 231, 163, 41, 213, 134, 233, 167, 254, 5, 3, 42, 193, 146, 99, 112, 139, 113, 46, 201, 128, 207, 44, 119, 142, 82, 205, 2, 8, 68, 180, 6, 76, 125, 183, 125, 52 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8