Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 989afd249244a35d578749e21debb5cd2c1b43fca90662b97777e89b17348a39

Tx prefix hash: 47584746d199693b0ca0a197e30c72597974f0ef32fced6c588b383250dc90e4
Tx public key: ddfdedb5610d89ad0cf5ec8c4cb4472e06fd60c81035d25b23f3e60b1c7253e9
Timestamp: 1767493645 Timestamp [UTC]: 2026-01-04 02:27:25 Age [y:d:h:m:s]: 00:044:03:06:14
Block: 1448171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 31383 RingCT/type: yes/0
Extra: 01ddfdedb5610d89ad0cf5ec8c4cb4472e06fd60c81035d25b23f3e60b1c7253e9020900000008f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b67fe20f9580bcfe5420d6af755ef7dff776da38abf3e2de89c982868d6b9a89 0.000600000000 1937135 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": 1448181, "vin": [ { "gen": { "height": 1448171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b67fe20f9580bcfe5420d6af755ef7dff776da38abf3e2de89c982868d6b9a89" } } ], "extra": [ 1, 221, 253, 237, 181, 97, 13, 137, 173, 12, 245, 236, 140, 76, 180, 71, 46, 6, 253, 96, 200, 16, 53, 210, 91, 35, 243, 230, 11, 28, 114, 83, 233, 2, 9, 0, 0, 0, 8, 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