Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dc9f440e6f5d4074297eec4294eb2af2a2fcf8a269ae85174d903a2101f528e

Tx prefix hash: aaa01d2e8524e3d3d3de6fe58c2eb23147b9cfba8a545724565b42a7a3140147
Tx public key: 039fb5b609af6f4f67dd383f35a050b85c0bc6619a4e3b4f76df1162fdc5806f
Timestamp: 1742305136 Timestamp [UTC]: 2025-03-18 13:38:56 Age [y:d:h:m:s]: 01:243:04:24:36
Block: 1242021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437793 RingCT/type: yes/0
Extra: 01039fb5b609af6f4f67dd383f35a050b85c0bc6619a4e3b4f76df1162fdc5806f0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 71d0085a15132174074e3c7fc8bc7e8b2bf7a23561a08fca61856f7042c9b59a 0.000600000000 1728994 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": 1242031, "vin": [ { "gen": { "height": 1242021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71d0085a15132174074e3c7fc8bc7e8b2bf7a23561a08fca61856f7042c9b59a" } } ], "extra": [ 1, 3, 159, 181, 182, 9, 175, 111, 79, 103, 221, 56, 63, 53, 160, 80, 184, 92, 11, 198, 97, 154, 78, 59, 79, 118, 223, 17, 98, 253, 197, 128, 111, 2, 17, 0, 0, 0, 8, 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: