Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d64cc1a78eb25f762415a497a8d14154310e4f6d758d44997b41bdb39562acde

Tx prefix hash: 85f48d52ebb1cb5f24b3cfc0dd54f2ef102b391f01c8ff3bacfe9fce2c71d312
Tx public key: e92025a0e284d6b708d062c9f68e72f4e795ba365c2e97a06ce41c8c1608e2c3
Timestamp: 1738453244 Timestamp [UTC]: 2025-02-01 23:40:44 Age [y:d:h:m:s]: 01:204:05:37:41
Block: 1210114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410351 RingCT/type: yes/0
Extra: 01e92025a0e284d6b708d062c9f68e72f4e795ba365c2e97a06ce41c8c1608e2c3021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f5e6d7eda35a87eec6eec4fe54df7ea29a682a86aebde3f7d221b285ebb2b4e9 0.000600000000 1696863 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": 1210124, "vin": [ { "gen": { "height": 1210114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5e6d7eda35a87eec6eec4fe54df7ea29a682a86aebde3f7d221b285ebb2b4e9" } } ], "extra": [ 1, 233, 32, 37, 160, 226, 132, 214, 183, 8, 208, 98, 201, 246, 142, 114, 244, 231, 149, 186, 54, 92, 46, 151, 160, 108, 228, 28, 140, 22, 8, 226, 195, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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: