Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90ebe9f7f82567a0f59610a93939ba01116801a95bb42b30fbc17f85166b1448

Tx prefix hash: 9472e23bf64b4499a79be871b74721351062c3d138395fc343fb60127f4b38dd
Tx public key: d545f3ab54f415edff10e98fac4e10d8dbe070d69cd190943e2aeb8cf88c7c18
Timestamp: 1770625686 Timestamp [UTC]: 2026-02-09 08:28:06 Age [y:d:h:m:s]: 00:007:00:01:05
Block: 1473954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 4972 RingCT/type: yes/0
Extra: 01d545f3ab54f415edff10e98fac4e10d8dbe070d69cd190943e2aeb8cf88c7c180208e5f5615d2ced7805

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ae42aeb5c2dc42b99de96cf5a5c5c042e15fc1d2faf6607266af014cffd609f8 0.000600000000 1963248 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": 1473964, "vin": [ { "gen": { "height": 1473954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae42aeb5c2dc42b99de96cf5a5c5c042e15fc1d2faf6607266af014cffd609f8" } } ], "extra": [ 1, 213, 69, 243, 171, 84, 244, 21, 237, 255, 16, 233, 143, 172, 78, 16, 216, 219, 224, 112, 214, 156, 209, 144, 148, 62, 42, 235, 140, 248, 140, 124, 24, 2, 8, 229, 245, 97, 93, 44, 237, 120, 5 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369