Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5194cf2a41af14bab5526d6c58b59e9f00ca3631c80a35288f9dfbf6b000b363

Tx prefix hash: 0b9857e02c642b23a749a400b218ddd2bd36b8234fe3aa14df414e368716febe
Tx public key: e6a6e0a8db36c4df0dbe3e760727245b796cde37ecfb69164629b367ed5d2ee5
Timestamp: 1770619954 Timestamp [UTC]: 2026-02-09 06:52:34 Age [y:d:h:m:s]: 00:006:13:19:57
Block: 1473909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 4651 RingCT/type: yes/0
Extra: 01e6a6e0a8db36c4df0dbe3e760727245b796cde37ecfb69164629b367ed5d2ee50208fd51de762b9bd6d3

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d02f05a1e2fefed9f5ac95f6fd8c01721bfb6e1ea7c1c9ebd89a60061b982978 0.000600000000 1963203 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": 1473919, "vin": [ { "gen": { "height": 1473909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d02f05a1e2fefed9f5ac95f6fd8c01721bfb6e1ea7c1c9ebd89a60061b982978" } } ], "extra": [ 1, 230, 166, 224, 168, 219, 54, 196, 223, 13, 190, 62, 118, 7, 39, 36, 91, 121, 108, 222, 55, 236, 251, 105, 22, 70, 41, 179, 103, 237, 93, 46, 229, 2, 8, 253, 81, 222, 118, 43, 155, 214, 211 ], "rct_signatures": { "type": 0 } }


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