Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 276889ea8283af02614b43df89499ee9595c05cfefa3f1e69a2eacabacc7c24e

Tx prefix hash: ccc310444e07a7810a67bbd884c836a934d4e761d7c902fa7127f45b2889a53a
Tx public key: 384d0142a736856b7348a55a0791913a1c2e2301201f8e9bdd2cafc1b14ec424
Timestamp: 1578635376 Timestamp [UTC]: 2020-01-10 05:49:36 Age [y:d:h:m:s]: 06:040:03:12:51
Block: 42242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1437410 RingCT/type: yes/0
Extra: 01384d0142a736856b7348a55a0791913a1c2e2301201f8e9bdd2cafc1b14ec4240211000000d4b221b3d1000000000000000000

1 output(s) for total of 0.444667678264 xmr

stealth address amount amount idx tag
00: 2bfa760efe7da38961be3dd5614d8e5e10b1b1e42f42d8bb1ec48d49874ad691 0.444667678264 76021 of 0 -

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": 42252, "vin": [ { "gen": { "height": 42242 } } ], "vout": [ { "amount": 444667678264, "target": { "key": "2bfa760efe7da38961be3dd5614d8e5e10b1b1e42f42d8bb1ec48d49874ad691" } } ], "extra": [ 1, 56, 77, 1, 66, 167, 54, 133, 107, 115, 72, 165, 90, 7, 145, 145, 58, 28, 46, 35, 1, 32, 31, 142, 155, 221, 44, 175, 193, 177, 78, 196, 36, 2, 17, 0, 0, 0, 212, 178, 33, 179, 209, 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