Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec9e3eebf3be0357d74b0e287482a364feb4160b3baf259658aee0bb91676de4

Tx prefix hash: 684be34d8ba5b4cf936f068662b791699efb9e97e2f84a292ec06eafb9f87dc8
Tx public key: edffabe44fed7ebcb23e9a18ecf67dcbbca65b133a966b784cdf67b964771619
Timestamp: 1748163292 Timestamp [UTC]: 2025-05-25 08:54:52 Age [y:d:h:m:s]: 00:353:14:38:37
Block: 1290511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242674 RingCT/type: yes/0
Extra: 01edffabe44fed7ebcb23e9a18ecf67dcbbca65b133a966b784cdf67b9647716190211000000039f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 891ac4756143eb4f2238b977441cd769935f236f2d6b2e7ee34f6e8e9254eb53 0.000600000000 1777980 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": 1290521, "vin": [ { "gen": { "height": 1290511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "891ac4756143eb4f2238b977441cd769935f236f2d6b2e7ee34f6e8e9254eb53" } } ], "extra": [ 1, 237, 255, 171, 228, 79, 237, 126, 188, 178, 62, 154, 24, 236, 246, 125, 203, 188, 166, 91, 19, 58, 150, 107, 120, 76, 223, 103, 185, 100, 119, 22, 25, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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: