Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e744118e1f4dc033ada718bc97b1d5dd742bb1d1ab997d52f841b1a8eb46bf

Tx prefix hash: 058f1a307b8ff165fec6a26577c70e29ad6cbd9e85c19ceb4ef1d39ec113520b
Tx public key: b257579f71bccc07451da7526c2d072dbb8617240ac9e9a043dcf4fc0e25f6fa
Timestamp: 1739960849 Timestamp [UTC]: 2025-02-19 10:27:29 Age [y:d:h:m:s]: 01:269:12:08:45
Block: 1222565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456644 RingCT/type: yes/0
Extra: 01b257579f71bccc07451da7526c2d072dbb8617240ac9e9a043dcf4fc0e25f6fa0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 860df2bc5e699feb04f83a573bf6e0301539b3f835c802b1bfd5df1f7c5a3578 0.000600000000 1709416 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": 1222575, "vin": [ { "gen": { "height": 1222565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "860df2bc5e699feb04f83a573bf6e0301539b3f835c802b1bfd5df1f7c5a3578" } } ], "extra": [ 1, 178, 87, 87, 159, 113, 188, 204, 7, 69, 29, 167, 82, 108, 45, 7, 45, 187, 134, 23, 36, 10, 201, 233, 160, 67, 220, 244, 252, 14, 37, 246, 250, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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: