Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b2cb8b8d90c0ce18e46c320a708f2c20fc28e962da1f2c5cad90548b66214d

Tx prefix hash: f0d7c091a95365059fac91da0863d97fee0423620c3b74731ce6da42d4f16c5a
Tx public key: 6b33109fc7350a706b137b89e8a3cc7a2dc9b6dcd16b3899eb9cd22c51a6623b
Timestamp: 1575384080 Timestamp [UTC]: 2019-12-03 14:41:20 Age [y:d:h:m:s]: 06:093:17:02:32
Block: 21437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1469637 RingCT/type: yes/0
Extra: 016b33109fc7350a706b137b89e8a3cc7a2dc9b6dcd16b3899eb9cd22c51a6623b020d3930303100020000000bc89603

1 output(s) for total of 0.521160143273 xmr

stealth address amount amount idx tag
00: 7053cd8055badd47c6e2c3d8e2b002a054eecae5949773cb52b593fd979e3ddb 0.521160143273 34088 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": 21447, "vin": [ { "gen": { "height": 21437 } } ], "vout": [ { "amount": 521160143273, "target": { "key": "7053cd8055badd47c6e2c3d8e2b002a054eecae5949773cb52b593fd979e3ddb" } } ], "extra": [ 1, 107, 51, 16, 159, 199, 53, 10, 112, 107, 19, 123, 137, 232, 163, 204, 122, 45, 201, 182, 220, 209, 107, 56, 153, 235, 156, 210, 44, 81, 166, 98, 59, 2, 13, 57, 48, 48, 49, 0, 2, 0, 0, 0, 11, 200, 150, 3 ], "rct_signatures": { "type": 0 } }


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