Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40bf84247d1008ddd85251f152c53fac970e354800d771f8c80b9d4b507d8be6

Tx prefix hash: 7ebb67ca5a04f45d566a9e57ec3ab348b4d8cba13b0dacd2fa8d386de0ba613a
Tx public key: 849cc6f7e3e744dc10cba39365ff8cc97c9b718b31dd15f49cccffcd9789a001
Timestamp: 1759325419 Timestamp [UTC]: 2025-10-01 13:30:19 Age [y:d:h:m:s]: 01:044:16:54:07
Block: 1380461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298238 RingCT/type: yes/0
Extra: 01849cc6f7e3e744dc10cba39365ff8cc97c9b718b31dd15f49cccffcd9789a0010211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 867d9291afd13f44c5ec45f1b06c01e1b7a371e3f2c1eaafacc10826aa785e42 0.000600000000 1868572 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": 1380471, "vin": [ { "gen": { "height": 1380461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "867d9291afd13f44c5ec45f1b06c01e1b7a371e3f2c1eaafacc10826aa785e42" } } ], "extra": [ 1, 132, 156, 198, 247, 227, 231, 68, 220, 16, 203, 163, 147, 101, 255, 140, 201, 124, 155, 113, 139, 49, 221, 21, 244, 156, 204, 255, 205, 151, 137, 160, 1, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: