Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eaaa20db53e48e1458dd3cb522fb65fd9701ca5bf9f3efe94d4cb8da7cae27c

Tx prefix hash: 0c2676a56b9ee4f83b8c9058ab5cdd70a2c7ff36140af408490aa6711ca8162d
Tx public key: 619e11bce5c511481ec85e5fee988a53dc100e22d0a60866365bd6fa9104d4e1
Timestamp: 1759110615 Timestamp [UTC]: 2025-09-29 01:50:15 Age [y:d:h:m:s]: 01:049:21:04:09
Block: 1378678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302023 RingCT/type: yes/0
Extra: 01619e11bce5c511481ec85e5fee988a53dc100e22d0a60866365bd6fa9104d4e1021100000004a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2cea752d6c43d0670e3ee570236f6e4ca8d101d1858523a295e58a9c33c98dfd 0.000600000000 1866773 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": 1378688, "vin": [ { "gen": { "height": 1378678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cea752d6c43d0670e3ee570236f6e4ca8d101d1858523a295e58a9c33c98dfd" } } ], "extra": [ 1, 97, 158, 17, 188, 229, 197, 17, 72, 30, 200, 94, 95, 238, 152, 138, 83, 220, 16, 14, 34, 208, 166, 8, 102, 54, 91, 214, 250, 145, 4, 212, 225, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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: