Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a49bb3020aede8fcde758749e1a19c7448b340e93e2d76f5aecfc17f683f3f9d

Tx prefix hash: 04a4b07166c5b9d4af5d84c0de874d4430a77617c8882a92f4a2472f0b4840ea
Tx public key: 213f093a4b3cc972e8ea69fa265bad6bf0a541684ed33ead42a50205ea276b2f
Timestamp: 1753260543 Timestamp [UCT]: 2025-07-23 08:49:03 Age [y:d:h:m:s]: 00:076:12:07:59
Block: 1331541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53436 RingCT/type: yes/0
Extra: 01213f093a4b3cc972e8ea69fa265bad6bf0a541684ed33ead42a50205ea276b2f02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c44fe8a7a822f1758c0287c7bda21cce67c768134a464aa1af31904189a454b 0.600000000000 1819336 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": 1331551, "vin": [ { "gen": { "height": 1331541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c44fe8a7a822f1758c0287c7bda21cce67c768134a464aa1af31904189a454b" } } ], "extra": [ 1, 33, 63, 9, 58, 75, 60, 201, 114, 232, 234, 105, 250, 38, 91, 173, 107, 240, 165, 65, 104, 78, 211, 62, 173, 66, 165, 2, 5, 234, 39, 107, 47, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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