Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f67778ebc2f858dc2bf98e3fb3ab6442ed5d08ec1f762038ca263bd7855ca402

Tx prefix hash: 1d473d43d44b89de258f9e010461d0bc4bf5b43dba554e796a89b5513a3f93c1
Tx public key: 6d85c5c33cd357a9b4480e3f13a0a4de1f8a4e9e166086c0fa294535d83ac708
Timestamp: 1772817747 Timestamp [UTC]: 2026-03-06 17:22:27 Age [y:d:h:m:s]: 00:260:07:52:09
Block: 1492076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191418 RingCT/type: yes/0
Extra: 016d85c5c33cd357a9b4480e3f13a0a4de1f8a4e9e166086c0fa294535d83ac70802110000000cf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cab7cec86aa1a8c9a6986cefde4322ede8e95b46b931f64e96a9ad03c1b00f50 0.000600000000 1981614 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": 1492086, "vin": [ { "gen": { "height": 1492076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cab7cec86aa1a8c9a6986cefde4322ede8e95b46b931f64e96a9ad03c1b00f50" } } ], "extra": [ 1, 109, 133, 197, 195, 60, 211, 87, 169, 180, 72, 14, 63, 19, 160, 164, 222, 31, 138, 78, 158, 22, 96, 134, 192, 250, 41, 69, 53, 216, 58, 199, 8, 2, 17, 0, 0, 0, 12, 241, 136, 200, 168, 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: