Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f270e5c66d8a3c71fee3c9eccbad84933a86556a506a5bd5bc0410da7e84e0f

Tx prefix hash: 0c3243b761de3bcecde5f5cfea15b930135f129ca3b210729bca9549992d39d5
Tx public key: 1f9a8e910a8fcc5124db8a1a3fa9d1865a9cc4090ec2961f8ea03c322a7ab421
Timestamp: 1739242849 Timestamp [UTC]: 2025-02-11 03:00:49 Age [y:d:h:m:s]: 01:282:05:12:43
Block: 1216652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465884 RingCT/type: yes/0
Extra: 011f9a8e910a8fcc5124db8a1a3fa9d1865a9cc4090ec2961f8ea03c322a7ab4210211000000051f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d3295002cc480ce204ca187e28455bf824c90c4109ab02677869f1eb71814bbb 0.000600000000 1703459 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 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": 1216662, "vin": [ { "gen": { "height": 1216652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3295002cc480ce204ca187e28455bf824c90c4109ab02677869f1eb71814bbb" } } ], "extra": [ 1, 31, 154, 142, 145, 10, 143, 204, 81, 36, 219, 138, 26, 63, 169, 209, 134, 90, 156, 196, 9, 14, 194, 150, 31, 142, 160, 60, 50, 42, 122, 180, 33, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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: