Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb0b6ac6bbe39754be2400177a6f171677ceba725678b4423a63139ea09014df

Tx prefix hash: 41bd9c8ee3c2f3edc5b659ec39f55c7d6ac7d42a38aea476ffcfe9bbc473a34e
Tx public key: 6292f329f283636120d5d41345154e375139e76bc68b19d8c347e814d19e018c
Timestamp: 1767581839 Timestamp [UTC]: 2026-01-05 02:57:19 Age [y:d:h:m:s]: 00:041:21:53:46
Block: 1448900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 29798 RingCT/type: yes/0
Extra: 016292f329f283636120d5d41345154e375139e76bc68b19d8c347e814d19e018c020900000016f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 66146095c7476c10cf56e0a74e45521251c9d27f1a9ddccab7b4d5e82c7c74f0 0.000600000000 1937878 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": 1448910, "vin": [ { "gen": { "height": 1448900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66146095c7476c10cf56e0a74e45521251c9d27f1a9ddccab7b4d5e82c7c74f0" } } ], "extra": [ 1, 98, 146, 243, 41, 242, 131, 99, 97, 32, 213, 212, 19, 69, 21, 78, 55, 81, 57, 231, 107, 198, 139, 25, 216, 195, 71, 232, 20, 209, 158, 1, 140, 2, 9, 0, 0, 0, 22, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


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