Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eeff932125385c0886c04ed97e05a71196331594fc2fd7444ddfeeeb54a0df1

Tx prefix hash: 6523f79f712c5863dc592c0fbd9fd8559d35e0b5498482983f32b2cab4bc181f
Tx public key: b659e242c5926389d355a4384e7002d2e8629ea98f97eac01dd9b9e0d28e6640
Timestamp: 1579018370 Timestamp [UTC]: 2020-01-14 16:12:50 Age [y:d:h:m:s]: 06:310:23:30:16
Block: 45407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1636579 RingCT/type: yes/0
Extra: 01b659e242c5926389d355a4384e7002d2e8629ea98f97eac01dd9b9e0d28e664002110000014bff58ae94000000000000000000

1 output(s) for total of 0.434066323926 xmr

stealth address amount amount idx tag
00: 367020f7b1c948d5c06bca7527e014b39cac8e6c91ca9e8a3216229bc56497de 0.434066323926 82958 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": 45417, "vin": [ { "gen": { "height": 45407 } } ], "vout": [ { "amount": 434066323926, "target": { "key": "367020f7b1c948d5c06bca7527e014b39cac8e6c91ca9e8a3216229bc56497de" } } ], "extra": [ 1, 182, 89, 226, 66, 197, 146, 99, 137, 211, 85, 164, 56, 78, 112, 2, 210, 232, 98, 158, 169, 143, 151, 234, 192, 29, 217, 185, 224, 210, 142, 102, 64, 2, 17, 0, 0, 1, 75, 255, 88, 174, 148, 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: