Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 417fd4781e797626d6a13650cd60ebec271d1abeebd5d1ac2d3258c665cfbeee

Tx prefix hash: 3a4ecd92db0a1b4e44dbf91506a0a2d629c71a2ca667e1ab0926de679161ea7d
Tx public key: b21f5e7fe2e45c71b4f215c4235ffcadddb48cc4abd3d117165a3fb57b5127c3
Timestamp: 1744165490 Timestamp [UTC]: 2025-04-09 02:24:50 Age [y:d:h:m:s]: 01:220:05:34:13
Block: 1257395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421359 RingCT/type: yes/0
Extra: 01b21f5e7fe2e45c71b4f215c4235ffcadddb48cc4abd3d117165a3fb57b5127c30211000000046c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 957379e95ef5aa8a44de9ff236dc2e9f0371a5855be38a6b96812dce9d15d2ca 0.000600000000 1744516 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": 1257405, "vin": [ { "gen": { "height": 1257395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "957379e95ef5aa8a44de9ff236dc2e9f0371a5855be38a6b96812dce9d15d2ca" } } ], "extra": [ 1, 178, 31, 94, 127, 226, 228, 92, 113, 180, 242, 21, 196, 35, 95, 252, 173, 221, 180, 140, 196, 171, 211, 209, 23, 22, 90, 63, 181, 123, 81, 39, 195, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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: