Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9619c5376826b19a0273c4e0e90a2a61cae361fe6cd2a3d2093300e53af72073

Tx prefix hash: e0ed68b0d62e74628c365e89955af40144ccce1039681c8adb3f11f5143c093e
Tx public key: 9040cdb9a6026ab295a61faa0984127728a7999797f3c1a5f1e9ea6bfaed71af
Timestamp: 1579440677 Timestamp [UTC]: 2020-01-19 13:31:17 Age [y:d:h:m:s]: 06:117:08:51:19
Block: 49052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1484857 RingCT/type: yes/0
Extra: 019040cdb9a6026ab295a61faa0984127728a7999797f3c1a5f1e9ea6bfaed71af021100000003bd0f9f9f000000000000000000

1 output(s) for total of 0.422154279225 xmr

stealth address amount amount idx tag
00: bd0f0ed790fdcb53022478e23fc057f7d03e8ba40abcb1e408bf89635d43d5f2 0.422154279225 90966 of 0 -

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 dinastycoin-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": 49062, "vin": [ { "gen": { "height": 49052 } } ], "vout": [ { "amount": 422154279225, "target": { "key": "bd0f0ed790fdcb53022478e23fc057f7d03e8ba40abcb1e408bf89635d43d5f2" } } ], "extra": [ 1, 144, 64, 205, 185, 166, 2, 106, 178, 149, 166, 31, 170, 9, 132, 18, 119, 40, 167, 153, 151, 151, 243, 193, 165, 241, 233, 234, 107, 250, 237, 113, 175, 2, 17, 0, 0, 0, 3, 189, 15, 159, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: