Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85e2c3d67c12e5050463a4ac215ee50766022b15c5abbe8b5b2c3b704ec3e138

Tx prefix hash: 59bfe8845acb67db628c102e2c89c5e5d7d03005e42df34e1e35bcf57853469d
Tx public key: e4ae1d095b261362022b07fcc3e47299e517817548fe0759bb27ef03b7613463
Timestamp: 1772216708 Timestamp [UTC]: 2026-02-27 18:25:08 Age [y:d:h:m:s]: 00:267:05:05:29
Block: 1487084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196410 RingCT/type: yes/0
Extra: 01e4ae1d095b261362022b07fcc3e47299e517817548fe0759bb27ef03b7613463021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e19f0fd98a3792349fccfcb019ae55afd8ab6346b85f9e77c99a26b3d46fd068 0.000600000000 1976546 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": 1487094, "vin": [ { "gen": { "height": 1487084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e19f0fd98a3792349fccfcb019ae55afd8ab6346b85f9e77c99a26b3d46fd068" } } ], "extra": [ 1, 228, 174, 29, 9, 91, 38, 19, 98, 2, 43, 7, 252, 195, 228, 114, 153, 229, 23, 129, 117, 72, 254, 7, 89, 187, 39, 239, 3, 183, 97, 52, 99, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: