Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0b57bf37eeeab370a84700c14145e7cd3cd8f4ef4a6e1d744ee24711504e7a0

Tx prefix hash: 6b2407033d39ff52a71ff486538319206b24e8af60e526aab499d66a9f8d489e
Tx public key: 5ba3e51078f878800c9e5a101ecb44135fbc86e543fbb068a60e4e071969fb68
Timestamp: 1772478460 Timestamp [UTC]: 2026-03-02 19:07:40 Age [y:d:h:m:s]: 00:263:21:15:32
Block: 1489263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194231 RingCT/type: yes/0
Extra: 015ba3e51078f878800c9e5a101ecb44135fbc86e543fbb068a60e4e071969fb68021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bbe5f0811d9724e75894abfb4b665b7a1a72a9fc6cbb7c63174d63554007b3de 0.000600000000 1978751 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": 1489273, "vin": [ { "gen": { "height": 1489263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbe5f0811d9724e75894abfb4b665b7a1a72a9fc6cbb7c63174d63554007b3de" } } ], "extra": [ 1, 91, 163, 229, 16, 120, 248, 120, 128, 12, 158, 90, 16, 30, 203, 68, 19, 95, 188, 134, 229, 67, 251, 176, 104, 166, 14, 78, 7, 25, 105, 251, 104, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: