Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a8f06df95941eb3779a6b9d6d1963aeb69e1bdea0bce01128d59e63e859d1c5

Tx prefix hash: bb19f80faff256811f64db1e32241cc9bcc29a15790da9a0a4829a236adea5da
Tx public key: 81dc6f04f9dc3a835df97a546c8a60cbe576880bcca580c77e2ac372723c821e
Timestamp: 1735347431 Timestamp [UTC]: 2024-12-28 00:57:11 Age [y:d:h:m:s]: 01:138:18:00:41
Block: 1184651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349911 RingCT/type: yes/0
Extra: 0181dc6f04f9dc3a835df97a546c8a60cbe576880bcca580c77e2ac372723c821e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a30e6bc04d40399caf8c8b97294470a20149dfccc5c89b8f764724fe9a6b15e2 0.000600000000 1671110 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": 1184661, "vin": [ { "gen": { "height": 1184651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a30e6bc04d40399caf8c8b97294470a20149dfccc5c89b8f764724fe9a6b15e2" } } ], "extra": [ 1, 129, 220, 111, 4, 249, 220, 58, 131, 93, 249, 122, 84, 108, 138, 96, 203, 229, 118, 136, 11, 204, 165, 128, 199, 126, 42, 195, 114, 114, 60, 130, 30, 2, 17, 0, 0, 0, 5, 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: