Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d19be9b2a487d7142d56f6868f11ce634f183e72f41a08d393ed5b8aa890bec

Tx prefix hash: cb8f356f0f13b60feee91aa56d9497341d3046f35576a0f06cdc233fbb1f3ad1
Tx public key: 222f4eb4765cf8ade7315a9785e8023ada09ba4c5f0829342d8ba2890b8a7c25
Timestamp: 1770641850 Timestamp [UTC]: 2026-02-09 12:57:30 Age [y:d:h:m:s]: 00:004:15:41:46
Block: 1474088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3294 RingCT/type: yes/0
Extra: 01222f4eb4765cf8ade7315a9785e8023ada09ba4c5f0829342d8ba2890b8a7c25021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 545e33a2a0485fbe3de6edef4d0aa668acbc75cd60f9082b4fd53021ac3833f6 0.000600000000 1963384 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": 1474098, "vin": [ { "gen": { "height": 1474088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "545e33a2a0485fbe3de6edef4d0aa668acbc75cd60f9082b4fd53021ac3833f6" } } ], "extra": [ 1, 34, 47, 78, 180, 118, 92, 248, 173, 231, 49, 90, 151, 133, 232, 2, 58, 218, 9, 186, 76, 95, 8, 41, 52, 45, 139, 162, 137, 11, 138, 124, 37, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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) | dinastycoin version: tesla-369