Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a394979598d319e631a3991ea386d8eb0f2b108b965bb3b4e71c5e15e1f0e5a6

Tx prefix hash: b6a359cd88b9355afeedede84639fe8f3ce0e92f480c05f1696aaaa7f39c26e5
Tx public key: f1865de2d2e3b656e029aaba0b124321b8d024ade9cdd4e78bef5683755c40e5
Timestamp: 1702712407 Timestamp [UTC]: 2023-12-16 07:40:07 Age [y:d:h:m:s]: 02:339:14:34:15
Block: 914229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 767975 RingCT/type: yes/0
Extra: 01f1865de2d2e3b656e029aaba0b124321b8d024ade9cdd4e78bef5683755c40e502110000000375e3f0e9000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 648f41a0a8387540a52eb2abc59af422abf32d06891a94db4b9e72af2f6d5a55 0.000600000000 1371515 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": 914239, "vin": [ { "gen": { "height": 914229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "648f41a0a8387540a52eb2abc59af422abf32d06891a94db4b9e72af2f6d5a55" } } ], "extra": [ 1, 241, 134, 93, 226, 210, 227, 182, 86, 224, 41, 170, 186, 11, 18, 67, 33, 184, 208, 36, 173, 233, 205, 212, 231, 139, 239, 86, 131, 117, 92, 64, 229, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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: