Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5468ebb6633ac04c419d2e01c182f991f63c331b58677d20855815f61dd8d03

Tx prefix hash: db3cb1450440e5023b6c062cd572acf87764c4663aa75b665a92a261bb751de1
Tx public key: f8220f9e64ed0c768e1f104b1c0b126e7308dbf7058605a1c2d872b6fbac4740
Timestamp: 1745078770 Timestamp [UTC]: 2025-04-19 16:06:10 Age [y:d:h:m:s]: 01:023:10:07:37
Block: 1264967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267559 RingCT/type: yes/0
Extra: 01f8220f9e64ed0c768e1f104b1c0b126e7308dbf7058605a1c2d872b6fbac474002110000000edbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 764520fe214a6e61eb3ac035f15c5e09620e260814411165be9f081306fe14ab 0.000600000000 1752170 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": 1264977, "vin": [ { "gen": { "height": 1264967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "764520fe214a6e61eb3ac035f15c5e09620e260814411165be9f081306fe14ab" } } ], "extra": [ 1, 248, 34, 15, 158, 100, 237, 12, 118, 142, 31, 16, 75, 28, 11, 18, 110, 115, 8, 219, 247, 5, 134, 5, 161, 194, 216, 114, 182, 251, 172, 71, 64, 2, 17, 0, 0, 0, 14, 219, 181, 113, 193, 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: