Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7c624d69a55fc4f7ec249f37c7cb3aebf9940a05ea43a3951ea942f2f5b4707

Tx prefix hash: 6ac6638c71c8fd4f50434154d59454b12aaa891157f1048f7842d515678494f7
Tx public key: e4f81776f1ce1057c00b5b06689c07461c5df8149f0f1394319730011d1f0d0f
Timestamp: 1743895315 Timestamp [UTC]: 2025-04-05 23:21:55 Age [y:d:h:m:s]: 00:330:13:33:01
Block: 1255161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233913 RingCT/type: yes/0
Extra: 01e4f81776f1ce1057c00b5b06689c07461c5df8149f0f1394319730011d1f0d0f0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 928d6fe220d66c653e901d04d87a60af781b42a48ce3d5efbd9cf5d73f4a249d 0.000600000000 1742264 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": 1255171, "vin": [ { "gen": { "height": 1255161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "928d6fe220d66c653e901d04d87a60af781b42a48ce3d5efbd9cf5d73f4a249d" } } ], "extra": [ 1, 228, 248, 23, 118, 241, 206, 16, 87, 192, 11, 91, 6, 104, 156, 7, 70, 28, 93, 248, 20, 159, 15, 19, 148, 49, 151, 48, 1, 29, 31, 13, 15, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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) | dinastycoin version: tesla-369