Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f50567be101dc0ead1805f42444541368709a8ed77acabb3bb1e609f5e200a48

Tx prefix hash: f1964b1f519dacbdfe385afc24732b9a36e721f274bbc63bb6c35ab5d97da2b3
Tx public key: 13dd7f51f574e775a2b49f51a65ef5f1562e21dacf5104435456f8222b741aa0
Timestamp: 1770275826 Timestamp [UTC]: 2026-02-05 07:17:06 Age [y:d:h:m:s]: 00:009:12:57:40
Block: 1471062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 6785 RingCT/type: yes/0
Extra: 0113dd7f51f574e775a2b49f51a65ef5f1562e21dacf5104435456f8222b741aa0020840bfd3722c087933

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fb56c343c5ca39e97dd0dc91ef11b7e8fe72f86b759e1e5aef917dd982fbc236 0.000600000000 1960332 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": 1471072, "vin": [ { "gen": { "height": 1471062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb56c343c5ca39e97dd0dc91ef11b7e8fe72f86b759e1e5aef917dd982fbc236" } } ], "extra": [ 1, 19, 221, 127, 81, 245, 116, 231, 117, 162, 180, 159, 81, 166, 94, 245, 241, 86, 46, 33, 218, 207, 81, 4, 67, 84, 86, 248, 34, 43, 116, 26, 160, 2, 8, 64, 191, 211, 114, 44, 8, 121, 51 ], "rct_signatures": { "type": 0 } }


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