Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c38f7a48e8a1f9cf077cb5395eb526687cb8db8dcc8dbc3eeb070517121ce9d

Tx prefix hash: fdf634b1418c9ec3d3183dd0aa3dc213f1387fef14629743b4fe6ac6acd845fd
Tx public key: 851a89648a1bec3adc7c5daaba2d2b1ea1bfcb0a4834516d3146834f9e02905a
Timestamp: 1733892300 Timestamp [UTC]: 2024-12-11 04:45:00 Age [y:d:h:m:s]: 01:157:23:49:05
Block: 1172642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363767 RingCT/type: yes/0
Extra: 01851a89648a1bec3adc7c5daaba2d2b1ea1bfcb0a4834516d3146834f9e02905a021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 91a2d9ca4b0d96502964616106ab97a64b646e44cb2fc5eaf4fc24ed56243a7e 0.000600000000 1658561 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": 1172652, "vin": [ { "gen": { "height": 1172642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91a2d9ca4b0d96502964616106ab97a64b646e44cb2fc5eaf4fc24ed56243a7e" } } ], "extra": [ 1, 133, 26, 137, 100, 138, 27, 236, 58, 220, 124, 93, 170, 186, 45, 43, 30, 161, 191, 203, 10, 72, 52, 81, 109, 49, 70, 131, 79, 158, 2, 144, 90, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: