Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3abd41241114f6111d887e29a01dab40fc14fffa778257f16c106b0a2f9ded63

Tx prefix hash: fc33a9313946704742c3978e0a50e27e4184314e92aa172d6ee4c4a2d2edca67
Tx public key: cbf6d30fcdadaf5047a822b63181938edbb7e37ed4df43c6e687d707b1baba25
Timestamp: 1743384524 Timestamp [UTC]: 2025-03-31 01:28:44 Age [y:d:h:m:s]: 01:048:00:10:49
Block: 1250926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285386 RingCT/type: yes/0
Extra: 01cbf6d30fcdadaf5047a822b63181938edbb7e37ed4df43c6e687d707b1baba250211000000019ba629df000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1ae2642439149411d151913c8d12f1f8c1a037550b1d316bd21fa029c0ee0f68 0.000600000000 1737985 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": 1250936, "vin": [ { "gen": { "height": 1250926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ae2642439149411d151913c8d12f1f8c1a037550b1d316bd21fa029c0ee0f68" } } ], "extra": [ 1, 203, 246, 211, 15, 205, 173, 175, 80, 71, 168, 34, 182, 49, 129, 147, 142, 219, 183, 227, 126, 212, 223, 67, 198, 230, 135, 215, 7, 177, 186, 186, 37, 2, 17, 0, 0, 0, 1, 155, 166, 41, 223, 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: