Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61b17ac84d2b80de4e39e3f7bdc2a5a131fe49c3001cc01b50fdbb396e483c5b

Tx prefix hash: 50aab33cc0a174f3a6bef4f7d59d6110be6acedb4399e224d149c38b0a5662cc
Tx public key: a4d40d09d308ffbc413210e6bd8e8bc0a7c77de6d4f8247b50da6636bd77ebc5
Timestamp: 1763977342 Timestamp [UCT]: 2025-11-24 09:42:22 Age [y:d:h:m:s]: 00:003:01:43:27
Block: 1419018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2206 RingCT/type: yes/0
Extra: 01a4d40d09d308ffbc413210e6bd8e8bc0a7c77de6d4f8247b50da6636bd77ebc50211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c5becc998c4cf7998b1e1fd489761143a8504b74f87d80226fcb495be012149 0.600000000000 1907553 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": 1419028, "vin": [ { "gen": { "height": 1419018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c5becc998c4cf7998b1e1fd489761143a8504b74f87d80226fcb495be012149" } } ], "extra": [ 1, 164, 212, 13, 9, 211, 8, 255, 188, 65, 50, 16, 230, 189, 142, 139, 192, 167, 199, 125, 230, 212, 248, 36, 123, 80, 218, 102, 54, 189, 119, 235, 197, 2, 17, 0, 0, 0, 1, 140, 235, 127, 9, 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