Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a3921189e9528723798a1a25629a23d7ab3bf862c7a83459434bc1ac29da7a0

Tx prefix hash: 4e4bc218030f5bef9db6a6e3b11069fe296f31183bc4f1a301346196b9150416
Tx public key: b7421ec2ab1fdb074775c162a7563b7f8ff3c57c2a61785eddd2ec455d3aa306
Timestamp: 1745773105 Timestamp [UCT]: 2025-04-27 16:58:25 Age [y:d:h:m:s]: 00:279:18:08:18
Block: 1270713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197572 RingCT/type: yes/0
Extra: 01b7421ec2ab1fdb074775c162a7563b7f8ff3c57c2a61785eddd2ec455d3aa3060211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36be22b7438ab95c422d3c65ce7d0675f236db04bf351a8ec9ac0f06364c474a 0.600000000000 1757958 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": 1270723, "vin": [ { "gen": { "height": 1270713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36be22b7438ab95c422d3c65ce7d0675f236db04bf351a8ec9ac0f06364c474a" } } ], "extra": [ 1, 183, 66, 30, 194, 171, 31, 219, 7, 71, 117, 193, 98, 167, 86, 59, 127, 143, 243, 197, 124, 42, 97, 120, 94, 221, 210, 236, 69, 93, 58, 163, 6, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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