Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d094a50c43561aabd8fadb60b2c6f18dc780b44d9592d5a718ee9ed382d5c13

Tx prefix hash: 4fd5f8212f1f3e066751ae2dda034cda61a2aa3fbb21bb8ab9fb9c10c7a39d29
Tx public key: 9b86d8ffaeab833ec55dbac85251703dd70a330e9a550ebedfb839e56f1f7e96
Timestamp: 1745853273 Timestamp [UTC]: 2025-04-28 15:14:33 Age [y:d:h:m:s]: 01:204:18:18:06
Block: 1271381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410410 RingCT/type: yes/0
Extra: 019b86d8ffaeab833ec55dbac85251703dd70a330e9a550ebedfb839e56f1f7e9602110000000325a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cc2217450581e33e50d4a737bbcc442bbfb1f5d41fdf91e4d67f14d161178b40 0.000600000000 1758642 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": 1271391, "vin": [ { "gen": { "height": 1271381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc2217450581e33e50d4a737bbcc442bbfb1f5d41fdf91e4d67f14d161178b40" } } ], "extra": [ 1, 155, 134, 216, 255, 174, 171, 131, 62, 197, 93, 186, 200, 82, 81, 112, 61, 215, 10, 51, 14, 154, 85, 14, 190, 223, 184, 57, 229, 111, 31, 126, 150, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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: