Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51ca864b1286853e371de9083dbc408a0e35ba2a4f333aecf742e0b8ff497234

Tx prefix hash: a444e8cea528ae1d1b13d6e2c486e4b63c1f2dc4dd69b4835ca092703cad8c5d
Tx public key: 6b07f5296b5a6cefb6d5ecf78c8b3ca2de6629f1fc417bb40ef2e98b896bc63d
Timestamp: 1725197524 Timestamp [UTC]: 2024-09-01 13:32:04 Age [y:d:h:m:s]: 02:078:18:38:40
Block: 1100649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 581096 RingCT/type: yes/0
Extra: 016b07f5296b5a6cefb6d5ecf78c8b3ca2de6629f1fc417bb40ef2e98b896bc63d021100000006e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 36d23fa7862c2e12386ddf58fc29d8d6213c3a76d46d835c148f28dc5c5822ae 0.000600000000 1576628 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": 1100659, "vin": [ { "gen": { "height": 1100649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d23fa7862c2e12386ddf58fc29d8d6213c3a76d46d835c148f28dc5c5822ae" } } ], "extra": [ 1, 107, 7, 245, 41, 107, 90, 108, 239, 182, 213, 236, 247, 140, 139, 60, 162, 222, 102, 41, 241, 252, 65, 123, 180, 14, 242, 233, 139, 137, 107, 198, 61, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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