Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea4c91fca5085fc1d0beac4ce748175d64b65051067c760d6e905f79032524ce

Tx prefix hash: 634ef88bff13b52478d0d0440a8b88af75593847ad1fce386a27d527ccd04f1a
Tx public key: 3367ca8d4d0904db4f0758d95639fb0d9ac977d29cc8e24b124302315b683d47
Timestamp: 1742899330 Timestamp [UTC]: 2025-03-25 10:42:10 Age [y:d:h:m:s]: 00:327:09:43:32
Block: 1246917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231646 RingCT/type: yes/0
Extra: 013367ca8d4d0904db4f0758d95639fb0d9ac977d29cc8e24b124302315b683d47021100000009c6740958000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d436ddb38ff396725e9a6c5520acd9ee832dfccbc228d9f3d93fbaad80e4c40f 0.000600000000 1733918 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": 1246927, "vin": [ { "gen": { "height": 1246917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d436ddb38ff396725e9a6c5520acd9ee832dfccbc228d9f3d93fbaad80e4c40f" } } ], "extra": [ 1, 51, 103, 202, 141, 77, 9, 4, 219, 79, 7, 88, 217, 86, 57, 251, 13, 154, 201, 119, 210, 156, 200, 226, 75, 18, 67, 2, 49, 91, 104, 61, 71, 2, 17, 0, 0, 0, 9, 198, 116, 9, 88, 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) | dinastycoin version: tesla-369